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/plangit clone --depth 1 https://github.com/queelius/claude-anvilWrote 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/queelius/claude-anvil/plan)<a href="https://agentmods.dev/commands/queelius/claude-anvil/plan"><img src="https://agentmods.dev/badge/commands/queelius/claude-anvil/plan.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.00012 | $0.00348 |
| Opus 5 | $0.00006 | $0.00174 |
| Sonnet 5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
plan 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
/bookwright:plan
Produce a per-chapter implementation plan from the relevant design spec. The plan is the basis for /bookwright:draft.
What it produces
A plan markdown file at docs/superpowers/plans/YYYY-MM-DD-<chapter-name>.md with:
- Goal, architecture summary, tech stack, scope, base SHA.
- Source-material list (which papers/sections to reformulate).
- Lessons inherited from prior plans (page-budget discipline, banned-phrase reminders, cross-ref discipline).
- File structure: which chapter and section subfiles get created.
- Cross-reference map: which labels this chapter defines and which it references.
- Per-task list (typically 8-10 tasks: scaffold + per-section + bib notes + exercises + notebook + integration).
- Each task with content checklist, page-budget target, header-comment-block requirement, commit message.
Steps
- Read the master spec and the relevant per-Part spec.
- Read the chapter's stub file in
book/chapters/if it exists. - Walk the per-section spec items from the per-Part spec; turn each into a Task with its content checklist.
- Add scaffold Task 1, bib-notes Task N-1, exercises Task N, and (if applicable) notebook Task N+1.
- Save the plan to the plans directory.
- Report it back; suggest next step:
/bookwright:draft <chapter>to execute the plan.
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 · 31 lines · 12 tokens per session scan A e48bce911a56
plan is a command published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 348 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
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.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
deps-age
Analyze dependency freshness and maintenance activity.
session-active
Set the persistent, per-session credo mode to active.
setup
Diagnose-first project setup with state machine — scans, confirms, interviews, writes.