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/cameronfreer/lean4-skills/autoformalizegit clone --depth 1 https://github.com/cameronfreer/lean4-skillsWrote 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/cameronfreer/lean4-skills/autoformalize)<a href="https://agentmods.dev/commands/cameronfreer/lean4-skills/autoformalize"><img src="https://agentmods.dev/badge/commands/cameronfreer/lean4-skills/autoformalize.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.00014 | $0.02350 |
| Opus 5 | $0.00007 | $0.01175 |
| Sonnet 5 | $0.00003 | $0.00470 |
| Haiku 4.5 | $0.00001 | $0.00235 |
Grade A, and why
autoformalize 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 5d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lean4 Autoformalize
Autonomous end-to-end formalization: extracts claims from a source, drafts Lean skeletons, and proves them — all unattended. Combines /lean4:draft and /lean4:autoprove in a single command.
Usage
/lean4:autoformalize --source ./paper.pdf --claim-select=first --out=Paper.lean
/lean4:autoformalize --source ./paper.pdf --claim-select=regex:"Theorem.*" --out=Paper.lean --rigor=checked
/lean4:autoformalize --source ./notes.md --claim-select=named:"Main Lemma" --out=Lemma.lean
Invocation Contract
Interpret this command's inputs per the Command Invocation Contract.
Primary path (hook-validated): If a validated-invocation block for this
command appears in context, treat it as the authoritative interpretation of
parser-decidable inputs and do not re-parse the raw invocation text for
those inputs. Start by reading all parser-decided fields from the block. Emit
the final Resolved Inputs summary from the block values.
See Validated Invocation Block.
Fallback path (other hosts): If no validated-invocation block is present,
parse the raw invocation text against this command's input table before
extracting claims or drafting anything.
Startup requirements:
- Emit a Resolved Inputs block with explicit values, defaults, coercions, ignored flags, and startup validation errors.
- Refuse to start on startup validation errors.
- Call
lean4-skills-cycle-tracker initwith resolved numeric values for--max-cycles,--max-stuck-cycles,--max-total-runtime, and--max-deep-per-cycle. A failed init (exit 2) is a startup validation error — do not proceed. - The state file is the single source of truth for session counters.
Read counters from
tick/statusoutput, not from conversational memory. - Per-claim lifecycle:
--max-cyclesand--max-stuck-cyclesare per-claim;--max-total-runtimeis per-session. Before each claim, callstart-claim. After each claim completes or stops (before the next), callreset-claim. The final claim does not needreset-claim— totals are accumulated live. See Claim Boundary Protocol.
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.
- 5d ago First seen · 159 lines · 14 tokens per session scan A 51ddc1113273
autoformalize is a command published in the GitHub repository cameronfreer/lean4-skills (430 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 2,350 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
draft
Draft Lean declaration skeletons from informal claims.
update_pandapower
This command updates the pandapower library to the latest version and synchronizes all skill files with the updated API.
lean
Drive a Lean / Mathlib formalization session using the lean skill.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.