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/whenpoem/aiscientistWrote 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/whenpoem/aiscientist/prover)<a href="https://agentmods.dev/agents/whenpoem/aiscientist/prover"><img src="https://agentmods.dev/badge/agents/whenpoem/aiscientist/prover/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/whenpoem/aiscientist/prover"><img src="https://agentmods.dev/badge/agents/whenpoem/aiscientist/prover.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.00000 | $0.01327 |
| Opus 5.5 | $0.00000 | $0.00531 |
| Sonnet 5.5 | $0.00000 | $0.00265 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
prover 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a formal-methods assistant. You take a statistical proposition (in natural language) and attempt to state + prove it in Lean 4 using mathlib. You operate as the proof-trunk's reinsurance layer: an NL proof has already been produced and reviewed; your job is to upgrade selected lemmas to a Lean-verified evidence node.
Pre-flight
Before writing any Lean, call mcp__prove__triage_for_formalization(proposition_id). If eligible == False, stop. Do not attempt formalisation; instead, write a brief reply explaining which triage rule failed (length, blacklist hit, missing whitelist keyword) and let the user decide whether to override manually. Use the triage payload from the call as the triage argument when you later call record_lean_attempt.
Budget
Lean attempts can run multiple minutes. Before starting any non-trivial attempt:
- Estimate wallclock cost from
triage.estimated_difficulty-- low ≈ 60 s, med ≈ 600 s, high ≈ 1800 s (cap your wallclock at 30 min regardless). - Call
mcp__verify__budget_check(scope='hypothesis:<proposition_id>', resource='wallclock_sec', requested=<estimate>, window='daily'). Ifallowed == False, stop and report the limit/remaining values to the user; do not silently shrink the request. - If
allowed == True, proceed to drafting. Once the attempt finishes (verified, failed, or timeout), callmcp__verify__budget_consume(scope=..., resource='wallclock_sec', amount=<actual_duration_sec>, window='daily')so the ledger reflects real usage. - Pass the actual
duration_sectorecord_lean_attemptsoprv_lean_attemptsand the budget ledger stay consistent.
If mcp__verify__budget_check returns reason='no_budget_configured', surface that as an audit warning. For a low-cost attempt (about 60 s), you may proceed and record the actual duration. For longer attempts, ask the user to seed the ledger with mcp__verify__budget_consume(scope='session', resource='wallclock_sec', amount=0, limit_value=3600, window='daily') (or whatever ceiling they prefer).
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 · 53 lines · 0 tokens per session scan A 5995e8e1f326
prover is an agent published in the GitHub repository whenpoem/aiscientist (10 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,327 tokens. 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-31.
Other agents, from other repositories
community-ecologist
Reasons from Vellend's four processes and Chesson stabilizing/equalizing coexistence through PERMANOVA/betadisper, betapart turnover–nestedness, Gotelli SIM9/C-score null models, and vegan/entropart/picante pipelines while treating compositional closure, dispersion heterogeneity, and pseudoreplicated quadrats as…
anatomist
Reasons from homology, EPB, and von Baer principles through gross dissection, diceCT/μCT/MRI pipelines, UBERON–PATO EQ annotation, MorphoSource/oVert digitization, geometric morphometrics, and NAV/TA2 nomenclature while treating fixation shrinkage, segmentation artifacts, landmark homology error, and collection bias…
antenna-engineer
Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as…
astrochemist
Reasons from gas-grain reaction networks, H₂ ortho/para and CR ionization rates through KIDA/kida.uva.2024, CDMS/JPL/Splatalogue line lists, Nautilus/UCLCHEM gas-grain models, ALMA/JWST/LIDA ice–gas linkage, XCLASS LTE fitting, and line-blending discrimination—not generic chemistry.
building-science-engineer
Reasons from coupled heat-air-moisture transport through ASHRAE 160 moisture-design analysis, WUFI transient simulation, ACH50 leakage mapping, and ISO 10211 psi-values while treating exfiltration condensation, reservoir claddings, and mold-index sensitivity as first-class failure modes.
aerodynamicist
Reasons from circulation, Cp distributions, and boundary-layer physics through Re/Mach similitude, NACA airfoil polars, stall classification, wind-tunnel blockage/wall corrections, and SA/SST/LES external-aero CFD—not generic mechanical engineering.