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/axiomantic/spellbook/docs-auditgit clone --depth 1 https://github.com/axiomantic/spellbookWhat 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.00030 | $0.02365 |
| Opus 5 | $0.00015 | $0.01182 |
| Sonnet 5 | $0.00006 | $0.00473 |
| Haiku 4.5 | $0.00003 | $0.00236 |
Grade A, and why
docs-audit 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MISSION
Analyze the target project to build a complete picture of its language, framework, existing documentation, API surface, and documentation gaps. Produce a structured DocsAuditResult that subsequent phases consume. Every field must be populated or explicitly defaulted with user interview fallback.
Invariant Principles
- Detect, don't assume: Scan package manifests and source files. Never guess language from directory names alone.
- Every field populated: A
DocsAuditResultwith null or empty fields causes downstream failures. If detection fails, interview the user via AskUserQuestion. - User chooses existing docs mode: Present all three options (audit+improve, start fresh, additive only). Never default silently.
- Graceful degradation: Missing manifest means interview the user, not a hard failure. Unsupported language means warn and default to MkDocs, not abort.
Execution Steps
Step 0: Create State Directory
PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
# Follows the spellbook project-encoded path convention (see managing-artifacts skill):
# strip leading slash, replace remaining slashes with dashes.
PROJECT_ENCODED=$(echo "$PROJECT_ROOT" | sed 's|^/||' | tr '/' '-')
mkdir -p ~/.local/spellbook/docs/$PROJECT_ENCODED/doc-state/
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.
- 2d ago First seen · 267 lines · 30 tokens per session scan A d4b544a2d540
docs-audit is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 2,365 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
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-repo-docs
Audit repository documentation against 85+ best practices from claude-code-ultimate-guide.
boldguy-linkedin-answer
Draft a LinkedIn comment on a post, referencing the guide's relevant section, in Flow style with AI markers removed.
methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
release
Release guide version (CHANGELOG + VERSION + README + landing sync + commit + push).