Automic VaultAutomic Vault

brew

claude-cmd mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für claude-cmd in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install claude-cmd

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Claude Code Commands Manager

Befehle und Aliase

  • claude-cmd

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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`.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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

Installierte Executables

BefehlArtSichtbarkeitHinweis
claude-cmdcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version1.1.1
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:claude-cmd
Version1.1.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/claude-cmd
Homepagehttps://github.com/kiliczsh/claude-cmd
Repositoryhttps://github.com/kiliczsh/claude-cmd
Upstream-Dokumentationhttps://claudecmd.com/
LizenzMIT
Quellarchivhttps://registry.npmjs.org/claude-cmd/-/claude-cmd-1.1.1.tgz
Abhängigkeitennode
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • 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