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.
git clone --depth 1 https://github.com/agent-anatomy/claudeWrote 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/commands/agent-anatomy/claude/deploy)<a href="https://agentmods.dev/commands/agent-anatomy/claude/deploy"><img src="https://agentmods.dev/badge/commands/agent-anatomy/claude/deploy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/agent-anatomy/claude/deploy"><img src="https://agentmods.dev/badge/commands/agent-anatomy/claude/deploy.svg" alt="Reviewed on agentmods" width="80" 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.00007 | $0.00086 |
| Opus 5.5 | $0.00003 | $0.00034 |
| Sonnet 5.5 | $0.00001 | $0.00017 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
deploy scanned grade A with 0 findings 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 1mo 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Prepare this branch for deployment.
Run in order:
npm run lint— fix any errors before continuingnpm test— all tests must passnpm run build— build must succeed- Summarize what's being deployed and flag anything risky
Do not proceed past any failing step. Report the failure clearly.
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.
- 1mo ago First seen · 14 lines · 7 tokens per session scan A 1649634c5df8
deploy is a command published in the GitHub repository agent-anatomy/claude (4 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 86 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
sdlc-cycle
An automated software development life-cycle (SDLC) workflow covering an issue or plan, coding, tests, verification, and a pull or merge request.
knowledge-graph
A visual map of how project guidance files are connected, including rules, memories, agents, skills, commands, and workflows. It generates a local HTML dashboard and can check whether their links still work.
skill-csk
Author or change a kit component (skill / agent / command) against the template and its gates.
gates-csk
Gate report — what the tool-level gates actually did, and which rules nothing has tripped.
fix-issue
A workflow for handling a numbered software issue from investigation through delivery. It reads the issue, changes the code, adds a regression test, verifies the build, and prepares a pull or merge request.
README
A reference guide for custom slash commands in an agent project. Each command is a named file that can receive text supplied after the command.