A revision coordinator for technical textbooks. It reads an existing review report, sends each finding to the appropriate writer or editor, and checks that the reported problems were fixed.

Use it to revise textbook prose, notebooks, and mechanical edits based on a completed review report. It can process selected severity levels and save a revision report.

It prevents review findings from being missed or rechecked inconsistently. It also leaves a record linking each fix to its original finding and verification.

rewriter — Agent for Claude Code by queelius/claude-anvil

Install

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.

Clone the repo

git clone --depth 1 https://github.com/queelius/claude-anvil

Made for: Claude Code.

Or install bookwright, the plugin that ships this one along with the rest of its 3 skills, 11 commands, 11 agents, 1 hook.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/queelius/claude-anvil/rewriter/github.svg)](https://agentmods.dev/agents/queelius/claude-anvil/rewriter)

Your own site

<a href="https://agentmods.dev/agents/queelius/claude-anvil/rewriter"><img src="https://agentmods.dev/badge/agents/queelius/claude-anvil/rewriter/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/queelius/claude-anvil/rewriter"><img src="https://agentmods.dev/badge/agents/queelius/claude-anvil/rewriter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 345 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,647 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.1	$0.00345	$0.01647
Opus 5.5	$0.00138	$0.00659
Sonnet 5.5	$0.00069	$0.00329
Haiku 4.5	$0.00034	$0.00165

Measured 1mo ago against content hash 052bc3b06240, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rewriter 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 1mo 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.

bookwright/agents/rewriter.md · 129 lines

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.

You orchestrate a revision pass on a technical textbook. You take a review report produced by the bookwright reviewer, fix what it found, verify each fix with the auditor that found it, and leave a paired, auditable record. You never re-review from scratch and you never freelance improvements beyond the findings.

Inputs

The launch prompt provides:

<report>: path to the review report (default: the newest docs/superpowers/reviews/YYYY-MM-DD-*.md that is not itself a -revision file)
<scope>: severity filter (blocking, substantive, minor, all; default all)
<output-path>: optional override directory for the revision report (the iterator uses this); without it, write <report-basename>-revision.md next to the source report
<mode>: interactive (default) or iterate (autonomous: best-guess low-stake judgments, defer high-stake ones to the report; never AskUserQuestion)

Finding-to-Fixer Mapping

Route each finding by its location's file type and its originating auditor (the report names the auditors per finding):

Finding	Fixer	Verifier
Prose/.tex content (pedagogy, missing checklist items, math errors in prose)	`bookwright:section-writer` with fix instructions	the originating auditor (`spec-auditor`, `quality-auditor`, or `math-auditor`)
Notebook findings (.ipynb / .Rmd / .qmd)	`bookwright:notebook-author` with fix instructions	`math-auditor` for numerical findings, `spec-auditor` for checklist findings
Mechanical items (labels, header comment blocks, notation lapses, formatting, citation keys)	you, direct Edit	`cross-ref-auditor` for label/ref items; the originating auditor otherwise

When one finding was flagged by multiple auditors, verify with the primary (first-listed) auditor.

Workflow

Phase 1: Comprehension

Read book/CLAUDE.md (build command, conventions, banned phrases) and the review report in full.
Parse every in-scope finding: id, severity, location (file:line), description, suggested fix, auditors.
Read each implicated file and confirm the finding still applies at the stated location. Findings whose subject text no longer exists are marked stale and reported, not fixed.

Read the full file on GitHub · 129 lines

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.

1mo ago First seen · 129 lines · 345 tokens per session scan A 052bc3b06240

Subscribe to this mod's changes

rewriter is an agent published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 3mo ago), licensed MIT. It adds 345 tokens to every session and 1,647 once invoked, about $0.0014 per session on Opus 5.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.

Claude Code Learning and teaching Writing and docs ai-tools claude claude-code-plugin

edtech-reviewer

Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…

avelikiy/great_cto · 112 tokens

ia-database-guardian

Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data. Postgres-specific query, index, and type patterns defer to the ia-postgresql skill; this agent is the migration-safety review gate.

iliaal/whetstone · 69 tokens

ia-best-practices-researcher

Researches external framework docs, version-specific constraints, and industry conventions for any technology. Use when you need authoritative external documentation.

iliaal/whetstone · 34 tokens

reviewer-opus

Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.

Joncik91/ucai · 32 tokens

kth

Cloud-native engineer and educator. Co-author of Kubernetes Up & Running (2017, 2019). Long-time Google Cloud Platform staff developer advocate (2014–2023, retired from full-time work). Best known for the "no-code" demo style that turns abstract distributed-systems concepts into running examples on stage. Authored…

punt-labs/punt-kit · 96 tokens

wiki-writer

Create or update wiki pages — autonomous ingest from any source, autonomous update. Auto-creates .wiki/ if missing.

Oshayr/LLM-Wiki · 28 tokens