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/frenzymath/ArchonWrote 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/commands/frenzymath/archon/autoprove)<a href="https://agentmods.dev/commands/frenzymath/archon/autoprove"><img src="https://agentmods.dev/badge/commands/frenzymath/archon/autoprove/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/commands/frenzymath/archon/autoprove"><img src="https://agentmods.dev/badge/commands/frenzymath/archon/autoprove.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.00014 | $0.03590 |
| Opus 5.5 | $0.00006 | $0.01436 |
| Sonnet 5.5 | $0.00003 | $0.00718 |
| Haiku 4.5 | $0.00001 | $0.00359 |
Grade A, and why
autoprove 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.
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lean4 Autoprove
Autonomous multi-cycle theorem proving. Runs cycles automatically with hard stop conditions and structured summaries.
Usage
/lean4:autoprove # Start autonomous session
/lean4:autoprove File.lean # Focus on specific file
/lean4:autoprove --repair-only # Fix build errors without filling sorries
/lean4:autoprove --max-cycles=10 # Limit total cycles
Inputs
| Arg | Required | Default | Description |
|---|---|---|---|
| scope | No | all | Specific file or theorem to focus on |
| --repair-only | No | false | Fix build errors only, skip sorry-filling |
| --planning | No | on | on or off |
| --review-source | No | internal | internal, external, both, or none (see coercion below) |
| --review-every | No | checkpoint | N (sorries), checkpoint, or never |
| --checkpoint | No | true | Create checkpoint commits after each cycle |
| --deep | No | stuck | never, stuck, or always (ask coerced to stuck — see Deep Mode) |
| --deep-sorry-budget | No | 2 | Max sorries per deep invocation |
| --deep-time-budget | No | 20m | Max time per deep invocation |
| --max-deep-per-cycle | No | 1 | Max deep invocations per cycle |
| --max-consecutive-deep-cycles | No | 2 | Hard cap on consecutive cycles using deep mode |
| --deep-snapshot | No | stash | V1: stash only |
| --deep-rollback | No | on-regression | on-regression, on-no-improvement, always, or never (see coercion below) |
| --deep-scope | No | target | target or cross-file |
| --deep-max-files | No | 2 | Max files per deep invocation |
| --deep-max-lines | No | 200 | Max added+deleted lines per deep invocation |
| --deep-regression-gate | No | strict | strict or off (see coercion below) |
| --batch-size | No | 2 | Sorries to attempt per cycle |
| --commit | No | auto | auto or never (ask coerced to auto — see note below) |
| --golf | No | never | prompt, auto, or never |
| --max-cycles | No | 20 | Hard stop: max total cycles |
| --max-total-runtime | No | 120m | Hard stop: max total runtime |
| --max-stuck-cycles | No | 3 | Hard stop: max consecutive stuck cycles |
| --formalize | No | never | never | restage | auto. See Formalize Outer Loop. (deprecated: use /lean4:autoformalize) |
| --source | No | — | File path, URL, or PDF for claim extraction. Required when --formalize=auto. (deprecated: use /lean4:autoformalize) |
| --claim-select | No | — | first | named:"..." | regex:"...". Queue-extraction filter applied once at startup. Required when --formalize=auto. Ignored without --source. (deprecated: use /lean4:autoformalize) |
| --formalize-rigor | No | sketch | sketch | checked. Rigor for formalize skeleton. (deprecated: use /lean4:autoformalize --rigor) |
| --statement-policy | No | preserve | preserve | rewrite-generated-only | adjacent-drafts. Default becomes rewrite-generated-only when --formalize=restage|auto (see flag validation). (deprecated: use /lean4:autoformalize) |
| --formalize-out | No | — | Target file for formalized claims. Required if no existing target in scope. (deprecated: use /lean4:autoformalize --out) |
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 · 241 lines · 14 tokens per session scan A 17104dae029e
autoprove is a command published in the GitHub repository frenzymath/Archon (228 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 3,590 once invoked, about $0.0001 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.
Other commands, from other repositories
verify-math
Verify a self-authored mathematical result end to end by routing claims across adversarial review, numerical falsification, symbolic or CAS checks, and Lean, then aggregating one report. Use when a theorem, proposition, conjecture, or paper-wide mathematical argument needs the appropriate combination of verification…
diff
Quantitative volume comparison between a CadQuery model and a reference STEP file.
arg-diagram
ARG academic-paper diagram mode — standalone structural & conceptual diagram generation.
plot
Publication Polish. Runs after results-analysis (Phase 7). Audits all tables and figures produced in Phases 4–7, upgrades them to top-journal standards by calling the table and figure skills.
graphite-morphology-classify
Classify graphite in a cast-iron micrograph per ASTM A247 / ISO 945-1, quantify nodularity, and read the matrix — the single most diagnostic observation in a cast-iron case.
checklist
Generate a custom checklist for the current feature based on user requirements.