Automic VaultAutomic Vault

brew

Install claude-cmd with Homebrew

Claude Code Commands Manager. Version 1.1.1 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install claude-cmd

local Homebrew formula metadata

overview

Package summary

Claude Code Commands Manager

Commands and aliases

  • claude-cmd

history

Project history and usage

claude-cmd is a small npm-distributed command manager for Claude Code users. Its official README positions it as a lightweight CLI for managing custom commands, Claude configuration files, security profiles, and MCP server settings.

Project history

The npm package was first published in July 2025, shortly after Claude Code created a market for reusable slash commands, CLAUDE.md files, and .claude project configuration. The project keeps the shape of a classic single-purpose developer CLI: install it globally, run `claude-cmd`, and use menus or subcommands to search, install, and manage Claude Code command assets.

The official README emphasizes command discovery, CLAUDE.md generation, local and remote command repositories, security profiles, and MCP integration. That makes the project part of the first wave of community tools that treated Claude Code configuration as packageable developer infrastructure rather than one-off dotfiles.

Adoption history

The package is distributed through npm as `claude-cmd`; the npm registry metadata records five published versions and published version 1.1.1. Homebrew also packages the npm tarball as formula `claude-cmd`, giving macOS and Linux users a package-manager install path alongside npm.

The source trail is narrow: official sources document npm and Homebrew distribution, but there is not enough primary evidence to claim broad adoption outside the Claude Code power-user niche.

How it is used

Typical use is interactive: run `claude-cmd` to browse command-management menus. The README also documents direct subcommands for listing installed commands, searching local or remote command repositories, installing a command, and showing version help.

The tool writes into Claude Code's normal configuration area, including `~/.claude/settings.json` and project `.claude/settings.json` or `.claude/settings.local.json`, so it complements rather than replaces Claude Code's own settings model.

Why package nerds care

For package-manager people, claude-cmd is interesting as a dotfile-era tool recast for AI coding agents: it packages prompts, slash commands, MCP references, and project instruction files into something discoverable and installable from a CLI.

Its Homebrew formula wraps an npm tarball, a common pattern for JavaScript CLIs that want to be available to users who think in `brew install` rather than `npm install -g`.

Timeline

  • 2025-07: npm registry records the first `claude-cmd` publication.
  • 2025-07: npm registry records published version 1.1.1 after five published versions.
  • 2026: Homebrew formula `claude-cmd` packages version 1.1.1 from the npm registry.

Related projects

  • Claude Code is the host tool whose commands and settings claude-cmd manages.
  • Model Context Protocol servers are part of the configuration surface the README says claude-cmd can manage.
  • Claude Code Templates is a related community catalog for agents, commands, hooks, MCPs, and settings.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 1 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
~/.claude/settings.json./.claude/settings.json./.claude/settings.local.json

executables

Installed executables

CommandKindExposureNote
claude-cmdcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version1.1.1
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/kiliczsh/claude-cmd

install metadata

Package metadata

Package keybrew:claude-cmd
Version1.1.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/claude-cmd
Homepagehttps://github.com/kiliczsh/claude-cmd
Repositoryhttps://github.com/kiliczsh/claude-cmd
Upstream docshttps://claudecmd.com/
LicenseMIT
Source archivehttps://registry.npmjs.org/claude-cmd/-/claude-cmd-1.1.1.tgz
Dependenciesnode
Bottleavailable (on all)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameclaude-cmd
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment