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 commands/tsmztech/claude-code-plugins/update-docsgit clone --depth 1 https://github.com/tsmztech/claude-code-pluginsWhat 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 | $0.00016 | $0.00443 |
| Opus 5 | $0.00008 | $0.00221 |
| Sonnet 5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
update-docs 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 yesterday.
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
Update claude-craft Reference Docs
Fetch all docs in parallel using background sub-agents, then update the manifest.
Step 1: Check versions
Run claude --version for the installed version and npm view @anthropic-ai/claude-code version for the latest available. If they differ, inform the user that a newer Claude Code version is available and suggest running claude update first — but proceed with the fetch if they want to continue.
Step 2: Spawn parallel sub-agents
Launch one background sub-agent per doc. Each sub-agent should:
- Read
${CLAUDE_PLUGIN_ROOT}/docs/cleanup-rules.mdfor what to strip - Fetch its assigned URL
- Apply the cleanup rules
- Save the cleaned content to
${CLAUDE_PLUGIN_ROOT}/docs/<filename>
| Fetch from | Save as |
|---|---|
| https://code.claude.com/docs/en/skills.md | skills.md |
| https://code.claude.com/docs/en/sub-agents.md | sub-agents.md |
| https://code.claude.com/docs/en/hooks-guide.md | hooks-guide.md |
| https://code.claude.com/docs/en/mcp.md | mcp.md |
| https://code.claude.com/docs/en/plugins.md | plugins.md |
| https://code.claude.com/docs/en/output-styles.md | output-styles.md |
| https://code.claude.com/docs/en/agent-teams.md | agent-teams.md |
Run all 7 in the background so they fetch concurrently.
Step 3: Update manifest
After all sub-agents complete, update ${CLAUDE_PLUGIN_ROOT}/docs/manifest.json:
- Set
claude_code_versionby runningclaude --version - Set
fetched_atto UTC now - Set
statusto"current"
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.
- yesterday First seen · 43 lines · 16 tokens per session scan A 088fafa5c85c
update-docs is a command published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 443 once invoked, about $0.0001 per session on Opus 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.