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/corvidae-coding-projects/thermite/acto-criticgit clone --depth 1 https://github.com/Corvidae-Coding-Projects/ThermiteWhat 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.00090 | $0.02174 |
| Opus 5 | $0.00045 | $0.01087 |
| Sonnet 5 | $0.00018 | $0.00435 |
| Haiku 4.5 | $0.00009 | $0.00217 |
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 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 — 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 matchconformance/<name>.cert.json(the golden certificate hand-derived fromthermite-design.md). - Wrong lowering —
thermite-loweremits Verus source that doesn't matchtests/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>".
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 · 129 lines · 90 tokens per session scan A d9816af9b79c
acto-critic is an agent published in the GitHub repository Corvidae-Coding-Projects/Thermite (53 stars, last pushed 25d ago), licensed MIT. It adds 90 tokens to every session and 2,174 once invoked, about $0.0005 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-30.
Other agents, from other repositories
program-logic
VCVio.ProgramLogic.Tactics.Relational; the umbrella import is still the intended default.
gotchas
Any file using evalSPMF, probOutput, probEvent, or Pr[...] on OracleComp spec needs [IsProbabilitySpec spec]. evalDist / 𝒟[…] also needs a MeasurableSpace on the result type. Lemmas that use uniform cardinalities, PMF.uniformOfFintype, or connect support to nonzero probability need [IsUniformSpec spec]. Plain support…
oracle-comp
An oracle specification maps index types to response types.
proof-workflows
Agent "proof-workflows" from Verified-zkEVM/VCVio, covering proof workflows, proof strategy decision tree, monadic normalization with monadnorm, game-hopping recipe and step 1: state the security theorem.
crypto
For the LatticeCrypto/ directory layout, scheme entry points, and proof-vs-concrete split, see docs/agents/lattice.md.
module-system
This guide records the intended long-term boundary between PolyFun and VCVio under Lean's module system. It is the decision record for visibility, import all, and the OracleComp/PFunctor.FreeM relationship.