Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/kiliczsh/claude-cmd/claude-mdgit clone --depth 1 https://github.com/kiliczsh/claude-cmdWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/kiliczsh/claude-cmd/claude-md)<a href="https://agentmods.dev/instructions/kiliczsh/claude-cmd/claude-md"><img src="https://agentmods.dev/badge/instructions/kiliczsh/claude-cmd/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00860 | $0.00860 |
| Opus 5 | $0.00430 | $0.00430 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade B, and why
claude-cmd CLAUDE.md scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. Global: `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Development Commands
Build & Development
npm run build- Compile TypeScript to dist/ and make executablenpm run dev- Watch TypeScript files for changes during developmentnpm run clean- Remove the dist directorynpm run link- Link the CLI globally for development testingnpm run prelink- Build before linking (runs automatically)
Command Processing
npm run parse-commands- Parse command markdown files to commands.jsonts-node scripts/parse-commands.ts- Direct script execution for command parsing
Testing
- No test framework configured yet (
npm testexits with error)
Architecture Overview
This is a TypeScript CLI tool for managing Claude commands, configurations, and workflows. The architecture follows a modular manager pattern:
Core Components
Main Entry Points:
src/index.ts- CLI entry point with command-line argument parsingsrc/cli.ts- Interactive CLI interface (ClaudeCommandCLIclass)
Core Services:
FileSystemManager(src/core/filesystem.ts) - Handles all file operations, directory managementClaudeCommandAPI(src/core/api.ts) - API abstraction for command fetching with caching- Command managers in
src/commands/- Specialized managers for different features
Manager Pattern: Each feature area has its own manager class:
CommandManager- Command installation, search, deletionClaudeMdManager- CLAUDE.md file managementPermissionsManager- Security and permissionsMCPManager- Model Context Protocol serversWorkflowManager- Command workflowsSettingsManager- Configuration managementProjectManager- Project initializationHelpManager- Documentation and help
Configuration System
Hierarchical Configuration:
- Global:
~/.claude/settings.json - Project:
./.claude/settings.json - Local overrides:
./.claude/settings.local.json
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 105 lines · 860 tokens per session scan B 288fb431a8b2
claude-cmd CLAUDE.md is an instructions file published in the GitHub repository kiliczsh/claude-cmd (312 stars, last pushed 8d ago), licensed MIT. It adds 860 tokens to every session, about $0.0043 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
framework AGENTS.md
AGENTS.md instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
safe-agentic-workflow AGENTS.md
AGENTS.md instructions for bybren-llc/safe-agentic-workflow, covering safe agent team quick reference, documentation, when to use which agent, auto-loaded skills and success validation commands.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.