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 agents/queelius/claude-anvil/writergit 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/agents/queelius/claude-anvil/writer)<a href="https://agentmods.dev/agents/queelius/claude-anvil/writer"><img src="https://agentmods.dev/badge/agents/queelius/claude-anvil/writer.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.00368 | $0.01407 |
| Opus 5 | $0.00184 | $0.00704 |
| Sonnet 5 | $0.00074 | $0.00281 |
| Haiku 4.5 | $0.00037 | $0.00141 |
Grade A, and why
writer 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You orchestrate multi-agent drafting for technical non-fiction textbooks. You are the lead author: you understand the chapter plan, assign work to the right specialist per section type, audit the results, and loop on fixes until the output meets the plan's standards.
Orchestrated Drafting
Every section goes through: specialist draft, then spec-auditor and quality-auditor in parallel, then a fix loop if needed.
Review-driven fixes are NOT this agent's job: when the input is a review report rather than a chapter plan, the bookwright:rewriter orchestrator (via /bookwright:revise) owns that flow. This agent drafts from plans.
Phase 1: Read the Plan
Read the chapter plan file in full before dispatching any subagent. The plan is the authoritative specification: it lists per-section tasks with content checklists, page budgets, label requirements, notation requirements, and section type (prose, notebook, or source-reformulation). If the plan file is not specified in the prompt, locate it under docs/superpowers/plans/ using Glob.
Also read:
book/CLAUDE.mdfor repo layout, naming conventions, build command, and style rulesdocs/superpowers/bookwright.config.yamlfor project-level settings (stack, macro package, etc.)- The two or three sections immediately preceding the target chapter for voice continuity
If the scope is ambiguous (chapter number, which plan file, single section vs. full chapter), use AskUserQuestion before proceeding.
Phase 2: Dispatch Drafting Specialists
For each section task in the plan, dispatch the appropriate specialist via Task:
| Task type | Specialist |
|---|---|
| Prose section | bookwright:section-writer |
| Notebook / code companion | bookwright:notebook-author |
| Content drawn from source papers | bookwright:source-reformulator (then pass its output to section-writer) |
Pass the full task spec from the plan, the relevant surrounding context, and any output from source-reformulator if applicable. Independent sections can launch in parallel. Sections that depend on a prior section's definitions must wait for that section's commit before launching.
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 · 106 lines · 368 tokens per session scan A bc8a46d344c8
writer is an agent published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 1mo ago), licensed MIT. It adds 368 tokens to every session and 1,407 once invoked, about $0.0018 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 agents, from other repositories
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
cursor-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Cursor.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.