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 commands/frenzymath/archon/provegit 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/prove)<a href="https://agentmods.dev/commands/frenzymath/archon/prove"><img src="https://agentmods.dev/badge/commands/frenzymath/archon/prove.svg" alt="Measured on agentmods" 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 | $0.00012 | $0.02337 |
| Opus 5 | $0.00006 | $0.01169 |
| Sonnet 5 | $0.00002 | $0.00467 |
| Haiku 4.5 | $0.00001 | $0.00234 |
Grade A, and why
prove 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 4d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lean4 Prove
Guided, cycle-by-cycle theorem proving. Asks before each cycle, supports deep escalation, and checkpoints your progress.
Usage
/lean4:prove # Start guided session
/lean4:prove File.lean # Focus on specific file
/lean4:prove --repair-only # Fix build errors without filling sorries
/lean4:prove --deep=stuck # Enable deep escalation when stuck
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 | ask | ask (prompt at startup), on, or off |
| --review-source | No | internal | internal, external, both, or none |
| --review-every | No | checkpoint | N (sorries), checkpoint, or never |
| --checkpoint | No | true | Create checkpoint commits after each cycle |
| --deep | No | never | never, ask, stuck, or always |
| --deep-sorry-budget | No | 1 | Max sorries per deep invocation |
| --deep-time-budget | No | 10m | Max time per deep invocation |
| --max-deep-per-cycle | No | 1 | Max deep invocations per cycle |
| --deep-snapshot | No | stash | V1: stash only |
| --deep-rollback | No | on-regression | on-regression, on-no-improvement, always, or never |
| --deep-scope | No | target | target or cross-file |
| --deep-max-files | No | 1 | Max files per deep invocation |
| --deep-max-lines | No | 120 | Max added+deleted lines per deep invocation |
| --deep-regression-gate | No | strict | strict (auto-abort on regression) or off |
| --batch-size | No | 1 | Sorries to attempt per cycle |
| --commit | No | ask | ask (prompt before each commit), auto, or never |
| --golf | No | prompt | prompt, auto, or never |
Startup Behavior
If key preferences are not passed via flags, ask once at startup:
Planning preference:
Start with a planning phase? (Recommended for new sessions)
- Yes — discover state, set scope, show plan (recommended)
- No — skip planning, start immediately
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.
- 4d ago First seen · 196 lines · 12 tokens per session scan A e73ef5d6031f
prove is a command published in the GitHub repository frenzymath/Archon (213 stars, last pushed 17d ago), licensed Apache-2.0. It adds 12 tokens to every session and 2,337 once invoked, about $0.0001 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 commands, from other repositories
training
Build the training plan for today (or a given date).
check-dev
Type-check a Z specification with fuzz.
me-figure-discussion
Write or review thermal-fluid figure discussion with observation, physical mechanism, comparison, uncertainty, and claim limits.
master_analysis
Run comprehensive 5-phase analysis across labs, genetics, and protocols.
run-panguweather
Guide the user through running PanguWeather end-to-end on an AMD cluster.
render-figures
Compile all .tex and .typ figure files in a directory.