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/thevibeworks/claude-code-docs/example-commandgit clone --depth 1 https://github.com/thevibeworks/claude-code-docsWrote 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/thevibeworks/claude-code-docs/example-command)<a href="https://agentmods.dev/commands/thevibeworks/claude-code-docs/example-command"><img src="https://agentmods.dev/badge/commands/thevibeworks/claude-code-docs/example-command.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.00014 | $0.00284 |
| Opus 5 | $0.00007 | $0.00142 |
| Sonnet 5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
example-command 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.
This is a copy
100% identical to example-command — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Example Command (Legacy commands/ Format)
Note: This demonstrates the legacy
commands/*.mdlayout. For new plugins, prefer theskills/<name>/SKILL.mddirectory format (seeskills/example-command/SKILL.mdin this plugin). Both are loaded identically — the only difference is file layout.
This command demonstrates slash command structure and frontmatter options.
Arguments
The user invoked this command with: $ARGUMENTS
Instructions
When this command is invoked:
- Parse the arguments provided by the user
- Perform the requested action using allowed tools
- Report results back to the user
Frontmatter Options Reference
Commands support these frontmatter fields:
- description: Short description shown in /help
- argument-hint: Hints for command arguments shown to user
- allowed-tools: Pre-approved tools for this command (reduces permission prompts)
- model: Override the model (e.g., "haiku", "sonnet", "opus")
Example Usage
/example-command my-argument
/example-command arg1 arg2
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 · 40 lines · 14 tokens per session scan A 809f5b818fce
example-command is a command published in the GitHub repository thevibeworks/claude-code-docs (39 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 284 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to example-command, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
reconcile
Check developer guides for documentation drift against recent code changes.
audit
Re-audit accepted ADRs against the codebase — verify each still holds, then amend, supersede, or deprecate the ones that don't.
review
Review proposed ADRs for lifecycle progression — accept implemented decisions, deprecate stale ones, archive trivial ones.
curate
Curate research files — inventory by type, identify stale/superseded candidates, update frontmatter status.
create
Create a new Architecture Decision Record.
from-spec
Extract Architecture Decision Records from a completed spec.