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/configuregit 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/configure)<a href="https://agentmods.dev/commands/thevibeworks/claude-code-docs/configure"><img src="https://agentmods.dev/badge/commands/thevibeworks/claude-code-docs/configure.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.00008 | $0.00692 |
| Opus 5 | $0.00004 | $0.00346 |
| Sonnet 5 | $0.00002 | $0.00138 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade C, and why
configure scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"description": "Warns about rm -rf commands" This is a copy
100% identical to configure — 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Hookify Rules
Load hookify:writing-rules skill first to understand rule format.
Enable or disable existing hookify rules using an interactive interface.
Steps
1. Find Existing Rules
Use Glob tool to find all hookify rule files:
pattern: ".claude/hookify.*.local.md"
If no rules found, inform user:
No hookify rules configured yet. Use `/hookify` to create your first rule.
2. Read Current State
For each rule file:
- Read the file
- Extract
nameandenabledfields from frontmatter - Build list of rules with current state
3. Ask User Which Rules to Toggle
Use AskUserQuestion to let user select rules:
{
"questions": [
{
"question": "Which rules would you like to enable or disable?",
"header": "Configure",
"multiSelect": true,
"options": [
{
"label": "warn-dangerous-rm (currently enabled)",
"description": "Warns about rm -rf commands"
},
{
"label": "warn-console-log (currently disabled)",
"description": "Warns about console.log in code"
},
{
"label": "require-tests (currently enabled)",
"description": "Requires tests before stopping"
}
]
}
]
}
Option format:
- Label:
{rule-name} (currently {enabled|disabled}) - Description: Brief description from rule's message or pattern
4. Parse User Selection
For each selected rule:
- Determine current state from label (enabled/disabled)
- Toggle state: enabled → disabled, disabled → enabled
5. Update Rule Files
For each rule to toggle:
- Use Read tool to read current content
- Use Edit tool to change
enabled: truetoenabled: false(or vice versa) - Handle both with and without quotes
Edit pattern for enabling:
old_string: "enabled: false"
new_string: "enabled: true"
Edit pattern for disabling:
old_string: "enabled: true"
new_string: "enabled: false"
6. Confirm Changes
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 · 129 lines · 8 tokens per session scan C 1cb84c1055f6
configure is a command published in the GitHub repository thevibeworks/claude-code-docs (39 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 692 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to configure, 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.