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/sdsrss/claudemd/claudemd-updategit clone --depth 1 https://github.com/sdsrss/claudemdWrote 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/sdsrss/claudemd/claudemd-update)<a href="https://agentmods.dev/commands/sdsrss/claudemd/claudemd-update"><img src="https://agentmods.dev/badge/commands/sdsrss/claudemd/claudemd-update.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.00033 | $0.00309 |
| Opus 5 | $0.00016 | $0.00154 |
| Sonnet 5 | $0.00007 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
claudemd-update 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 today.
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
Usage: /claudemd-update
Run: node ${CLAUDE_PLUGIN_ROOT}/scripts/update.js (dry-run summary first).
If the user says apply, re-run with choice=apply-all via CLAUDEMD_UPDATE_CHOICE=apply-all node ${CLAUDE_PLUGIN_ROOT}/scripts/update.js. Backup is automatic (retained to 5). Do not fetch from GitHub — plugin fetching is a separate step owned by CC. Canonical plugin refresh: /claudemd-refresh (one command; restart afterwards). Manual fallback (paste each line):
/plugin marketplace update claudemd
/plugin uninstall claudemd@claudemd
/plugin install claudemd@claudemd
/reload-plugins
Note: /plugin update is not a real CC command.
Per-file select is not supported. The 4-file spec set (CLAUDE.md + CLAUDE-extended.md + CLAUDE-changelog.md + OPERATOR.md) evolves lockstep — CLAUDE.md H1 is the canonical version, and §EXT §X-EXT cross-references would dangle if only some files updated. Choices are apply-all (full 4-file sync) or cancel.
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.
- today Changed 536687e90665
- 5d ago First seen · 22 lines · 33 tokens per session scan A 8b9c97d3e36e
claudemd-update is a command published in the GitHub repository sdsrss/claudemd (2 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 309 once invoked, about $0.0002 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
brooks-health
Run a Brooks-Lint codebase health dashboard across all four dimensions.
brooks-debt
Run a Brooks-Lint tech debt assessment.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.