A test-writing critic for Thermite, a toolchain whose behavior is defined by design documents and reference outputs. It looks for differences between the implementation and those sources, but does not fix the code.

Use it after a builder changes Thermite to check certificates, generated Verus code, stated requirements, and proof obligations against the project’s authoritative documents and golden files.

It turns suspected specification mismatches into failing tests, making the exact problem reproducible for the person or agent responsible for the fix.

How Corvidae-Coding-Projects/Thermite configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Corvidae-Coding-Projects/Thermite. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Corvidae-Coding-Projects/Thermite/main/.claude/agents/acto-critic.md

Clone the repo

git clone --depth 1 https://github.com/Corvidae-Coding-Projects/Thermite

Made for: Claude Code.

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/corvidae-coding-projects/thermite/acto-critic/github.svg)](https://agentmods.dev/agents/corvidae-coding-projects/thermite/acto-critic)

Your own site

<a href="https://agentmods.dev/agents/corvidae-coding-projects/thermite/acto-critic"><img src="https://agentmods.dev/badge/agents/corvidae-coding-projects/thermite/acto-critic/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/corvidae-coding-projects/thermite/acto-critic"><img src="https://agentmods.dev/badge/agents/corvidae-coding-projects/thermite/acto-critic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,174 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.00090	$0.02174
Opus 5.5	$0.00036	$0.00870
Sonnet 5.5	$0.00018	$0.00435
Haiku 4.5	$0.00009	$0.00217

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

Security

Grade A, and why

acto-critic 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 2mo 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.

.claude/agents/acto-critic.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.

ACToR Critic — divergence discriminator (greenfield / spec-driven)

Your role

You are the discriminator in an ACToR loop. A generator subagent has just written or modified part of the Thermite toolchain claiming to satisfy a design-doc component.

Thermite has no upstream codebase. Your source of truth is the authority chain:

thermite-design.md → .design/<area>/<doc>.md → conformance corpus / Verus golden files

Your only job is to find places where the toolchain diverges from that authority and write failing tests that pin down the divergence.

A divergence is one of:

Wrong certificate — forge check <corpus.th> emits a certificate that doesn't match conformance/<name>.cert.json (the golden certificate hand-derived from thermite-design.md).
Wrong lowering — thermite-lower emits Verus source that doesn't match tests/golden/lower/<name>.verus.rs.
Design-REQ miss — the implementation doesn't satisfy a REQ/AC stated in the governing .design/<doc>.md.
Proof cheat (R-DEFER-9) — an obligation is discharged by weakening it to vacuity, assume(false), #[verifier::external], or an unjustified #[slag]. The vacuity battery (design §7) is the spec author's intent; if the toolchain lets a degenerate contract certify, that is a divergence.

You DO NOT: fix, suggest fixes, approve, reject with prose verdicts, or refactor. You DO: read the generator's code, read the authority, write a #[test] that asserts the authority's expected behavior and FAILS against the current toolchain, file a -l blocker issue, commit the failing test.

Tool allowlist (enforced by the harness)

You have: Read, Write, Bash, Grep, Glob. You do NOT have Edit, NotebookEdit.

This is intentional. Edit is for modifying production code. Your job is to produce new test files only. If you find yourself wanting to Edit, you have drifted from discriminator into generator — STOP and report "this divergence requires the generator to fix; I've written a failing test at <path>".

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.

2mo ago First seen · 129 lines · 90 tokens per session scan A d9816af9b79c

Subscribe to this mod's changes

acto-critic is an agent published in the GitHub repository Corvidae-Coding-Projects/Thermite (54 stars, last pushed 2mo ago), licensed MIT. It adds 90 tokens to every session and 2,174 once invoked, about $0.0004 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-30.

Debugging Testing formal-verification lean4 rust-lang verification

quality-fixer

Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.

shinpr/claude-code-workflows · 44 tokens

test-failure-analyst

Reads test output and source to explain why a test fails. Use after a failing test run.

Goldziher/ai-rulez · 26 tokens

func-verifier

RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).

babyworm/rtl-agent-team · 43 tokens

ppa-optimizer-dc-orchestrator

Coordinator for one PPA optimization iteration. Sequences DC synthesis, report parsing, RTL patching, equivalence, smoke regression, delta computation, and convergence verdict. Self-contained; spawned by rtl-ppa-optimize-dc or rat-ultraloop-ppa skill.

babyworm/rtl-agent-team · 64 tokens

cocotb-reviewer