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/agents/frenzymath/archon/lean4-axiom-eliminator)<a href="https://agentmods.dev/agents/frenzymath/archon/lean4-axiom-eliminator"><img src="https://agentmods.dev/badge/agents/frenzymath/archon/lean4-axiom-eliminator/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/agents/frenzymath/archon/lean4-axiom-eliminator"><img src="https://agentmods.dev/badge/agents/frenzymath/archon/lean4-axiom-eliminator.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.00044 | $0.00993 |
| Opus 5 | $0.00022 | $0.00496 |
| Sonnet 5 | $0.00009 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
lean4-axiom-eliminator 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 10d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inputs
- File or project to audit
- List of custom axioms to eliminate
- Permission level for refactoring
Actions
-
Audit current state:
- Start with
lean_diagnostic_messages(file)on the target file(s) before broader verification - Use
bash $LEAN4_SCRIPTS/check_axioms_inline.sh FILE.lean(or.for project-wide audit) to measure current axiom state - Use
bash $LEAN4_SCRIPTS/find_usages.sh axiom_namefor dependency inventory
- Start with
-
Propose migration plan (~500-800 tokens):
## Axiom Elimination Plan **Total custom axioms:** N **Target:** 0 ### Inventory 1. **axiom_1** - Type: [mathlib_search|compositional|structural] Used by: M theorems, Priority: high/medium/low ### Elimination Order Phase 1: Low-hanging fruit (mathlib_search) Phase 2: Medium difficulty (compositional) Phase 3: Hard cases (structural/convert to sorry) -
Execute batch by batch - For each axiom:
- Search via LSP first (
lean_leanfinder,lean_local_search), then script fallback - If found: import and replace
- If not: compose from mathlib lemmas
- If stuck: convert to
theorem ... := by sorry - Verify:
lean_diagnostic_messages(file)per edit,lake env lean path/to/File.leanfor file gate (run from the project root), axiom count decreased; reservelake buildfor final/project gate
- Search via LSP first (
-
Report progress after each elimination and final summary
Output
Per-axiom report (~200-400 tokens):
## Axiom Eliminated: axiom_name
**Strategy:** mathlib_import/compositional/converted_to_sorry
**Changes:** [imports, helpers]
**Verification:** Compile ✓, Count N→N-1 ✓
Final summary (~300-500 tokens):
## Axiom Elimination Complete
**Starting:** N, **Ending:** M
**By strategy:** X mathlib, Y compositional, Z sorry
**Files changed:** K
Total: ~2000-3000 tokens per batch
Constraints
- Lemma search required before proving (LSP-first, script fallback)
- Compile and verify after EACH elimination
- May NOT add new axioms while eliminating
- May NOT skip lemma search
- May NOT break dependent theorems
- Must track axiom count (trending down)
- Prefer live-file MCP for target-context verification; use
lean_run_codefor isolated scratch experiments, and temporary.leanfiles only iflean_run_codeis unavailable or insufficient
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.
- 10d ago First seen · 115 lines · 44 tokens per session scan A 0f6a66eb1952
lean4-axiom-eliminator is an agent published in the GitHub repository frenzymath/Archon (216 stars, last pushed 24d ago), licensed Apache-2.0. It adds 44 tokens to every session and 993 once invoked, about $0.0002 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
algorithm-reviewer
Use when code contains non-trivial algorithms, loops, recursion, or data-structure choices — the specialist that analyzes the time/space complexity (Big-O) of every routine and proposes a lower-complexity algorithm or data structure where one exists. Verifies against the performance and scientific persona standards.
Geographer
Expert in physical and human geography, climate systems, cartography, and spatial analysis — builds geographically coherent worlds where terrain, climate, resources, and settlement patterns make scientific sense.
Drone/Reality Mapping Specialist
Photogrammetry and reality capture expert who processes drone imagery into orthomosaics, digital terrain models, point clouds, and 3D meshes — bridging field capture and GIS-ready products.
GeoAI/ML Engineer
Geospatial machine learning specialist who builds models for feature extraction, object detection, image segmentation, and land cover classification from satellite and aerial imagery.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
GIS Analyst
Day-to-day GIS operator who creates maps, manages layers, performs spatial queries, and maintains geospatial data integrity across desktop and web environments.