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/queelius/claude-anvil/helpgit clone --depth 1 https://github.com/queelius/claude-anvilWhat 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.00011 | $0.00534 |
| Opus 5 | $0.00005 | $0.00267 |
| Sonnet 5 | $0.00002 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
help 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.
What it actually says
/bookwright:help
Print a quick reference.
Commands
/bookwright:init [name]: scaffold a fresh book project./bookwright:design [master | partN]: write a design spec via Socratic dialogue./bookwright:plan <chapter>: write a per-chapter implementation plan from the spec./bookwright:draft <chapter | section>: launch the writer orchestrator./bookwright:notebook <chapter>: draft and execute the paired notebook./bookwright:check [scope]: mechanical diagnostics (build, labels, page audit, threads, hooks)./bookwright:review [scope]: heavy multi-agent editorial review./bookwright:revise [report]: apply a review report's findings (fix-then-verify)./bookwright:iterate [scope]: review-fix-review loop until convergence./bookwright:integrate [scope]: per-Part or full-book integration check plus written record./bookwright:help: this reference.
Agents (v0.2)
Orchestrators: writer, reviewer, rewriter, iterator. Drafting specialists: section-writer, notebook-author, source-reformulator. Review specialists: spec-auditor, quality-auditor, math-auditor, cross-ref-auditor.
Skills (auto-triggered)
bookwright:textbook-methodology: prose-drafting tasks.bookwright:cross-reference-discipline: cross-referenced sections.bookwright:notebook-paired-with-prose: notebook tasks.
Hooks
- Soul-voice (banned-phrase enforcement): provided by the
soulplugin. - LaTeX-macro-leak: provided by bookwright itself.
Typical workflow
/bookwright:init mybookthencd mybook./bookwright:design master, then/bookwright:design part1, etc.- For each chapter:
/bookwright:plan chN, then/bookwright:draft chN. - Chapter polish:
/bookwright:review chNthen/bookwright:revise, or just/bookwright:iterate chN. - Per-Part close:
/bookwright:integrate part1. - Full-book close:
/bookwright:integrate book.
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 · 48 lines · 11 tokens per session scan A aed8fd614627
help is a command published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 534 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
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
validate-dependencies
Validate all task dependencies for issues.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.