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-togglegit 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-toggle)<a href="https://agentmods.dev/commands/sdsrss/claudemd/claudemd-toggle"><img src="https://agentmods.dev/badge/commands/sdsrss/claudemd/claudemd-toggle.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 | $0.00027 | $0.00169 |
| Opus 5 | $0.00014 | $0.00084 |
| Sonnet 5 | $0.00005 | $0.00034 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
claudemd-toggle 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 3d 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
Usage: /claudemd-toggle <hook-name>
Valid hook names: session-start-check, version-sync, memory-prompt-hint, pre-bash-safety, banned-vocab, ship-baseline, memory-read-check, session-extended-read, residue-audit, sandbox-disposal-check, mem-audit, session-summary, transcript-vocab-scan, transcript-structure-scan, session-end-check.
Run: node ${CLAUDE_PLUGIN_ROOT}/scripts/toggle.js $ARGS
Surface the new state (enabled or disabled) to the user.
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.
- 3d ago First seen · 13 lines · 27 tokens per session scan A b7b6e7d698d0
claudemd-toggle is a command published in the GitHub repository sdsrss/claudemd (2 stars, last pushed 10d ago), licensed MIT. It adds 27 tokens to every session and 169 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
VibeGuard: Learn
Dual-mode learning: (A) Extract guard rules from errors (B) Extract reusable skills from discoveries. Automatic mode routing.
VibeGuard: Cross Review
Dual-model adversarial review — Claude generates review reports, Codex does adversarial verification, and iterates until convergence.
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Preflight
Explore the project before major modifications, generate constraint sets, and prevent problems from the source.
VibeGuard: Check
Run all guard scripts with one click and output project health report.
VibeGuard: Interview
In-depth interviews with user needs before the start of major functions, mining boundary conditions and technical trade-offs, and outputting structured SPEC.