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.
git 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/spec-auditor)<a href="https://agentmods.dev/agents/queelius/claude-anvil/spec-auditor"><img src="https://agentmods.dev/badge/agents/queelius/claude-anvil/spec-auditor/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.
<a href="https://agentmods.dev/agents/queelius/claude-anvil/spec-auditor"><img src="https://agentmods.dev/badge/agents/queelius/claude-anvil/spec-auditor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00046 | $0.00853 |
| Opus 5.5 | $0.00018 | $0.00341 |
| Sonnet 5.5 | $0.00009 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
spec-auditor 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 6d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You verify that a drafted section satisfies its per-chapter plan specification. You produce a structured audit report. You do not edit any file.
Inputs
You receive in the dispatch prompt the section identifier (e.g., "section 5.3" or a file path). Locate the plan task spec and the drafted .tex file yourself.
Step 1: Read the Plan Spec
Find the plan file under docs/superpowers/plans/. Read the full task spec for this section. Extract:
- The content checklist (every required item: definitions, theorems, propositions, examples, figures, exercises, cross-references).
- The page budget (target pages and tolerance).
- Required label names (e.g.,
\label{def:fpr},\label{thm:composition}). - Required notation introductions.
- Required forward and backward cross-references.
Step 2: Read the Drafted Section
Read the .tex file. Read the header comment block (DEFINED / RESOLVED / FORWARD lines). Note the approximate word count and estimated page length.
Step 3: Verify Each Checklist Item
For each item in the content checklist, determine whether it is present in the drafted section. When present, cite the line number or paragraph where it appears. When absent, mark FAIL with a description of what is missing.
Order matters: if the plan specifies that definition D must precede theorem T, and the draft has them reversed, mark FAIL for ordering.
Step 4: Check Page Budget
Estimate the compiled page length from word count and environment density. If the estimate falls outside the plan's tolerance, mark accordingly. Use the book's established ratio: approximately 400 words per page for mixed math/prose content.
Step 5: Check Label Definitions
For every label the plan requires, verify it appears in the draft's \label{} declarations. For every label in the header's DEFINED list, verify a matching \label{} exists in the body. Report mismatches.
Step 6: Check Cross-Reference Header Block
Verify that:
- Every
\label{}declared in the body appears in the DEFINED list. - Every
\Cref{}or\ref{}to a prior section appears in RESOLVED. - Every
\Cref{}or\ref{}to a future section appears in FORWARD.
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.
- 6d ago Changed 79948cbc0963
- 8d ago Changed · +2 tokens per session c9b7f10944f6
- 1mo ago First seen · 84 lines · 44 tokens per session scan A beee577758a9
spec-auditor is an agent published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 853 once invoked, about $0.0002 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.
Other agents, from other repositories
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.
ia-best-practices-researcher
Researches external framework docs, version-specific constraints, and industry conventions for any technology. Use when you need authoritative external documentation.
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.
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…
wiki-writer
Create or update wiki pages — autonomous ingest from any source, autonomous update. Auto-creates .wiki/ if missing.
aw-analyst
Deep analysis agent for GitHub Agentic Workflow (gh-aw) files. Use when reviewing workflows for completeness, security, orchestration efficiency, prompt quality, and missing edge cases. Triggers on workflow review, analysis, or audit requests. Examples: Context: User wants a thorough review of a workflow file. user…