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 skills/morankor/theorist-toolbox/math-proofnpx skills add morankor/theorist-toolbox --skill math-proofgit clone --depth 1 https://github.com/morankor/theorist-toolboxWrote 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/skills/morankor/theorist-toolbox/math-proof)<a href="https://agentmods.dev/skills/morankor/theorist-toolbox/math-proof"><img src="https://agentmods.dev/badge/skills/morankor/theorist-toolbox/math-proof.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.1 | $0.00064 | $0.00696 |
| Opus 5 | $0.00032 | $0.00348 |
| Sonnet 5 | $0.00013 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
math-proof 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 6d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Math Proof
Write proofs suitable for a paper draft. The deliverable is a complete proof, not an outline. Every transition must be checkable by a skeptical reader without filling in missing algebra, sign arguments, or quantifier choices.
This skill adapts Moran Koren's Theorist Toolbox proof discipline for Codex. Preserve the core invariant: if a step is not proved, cited, or explicitly marked as conjectural, do not present it as established.
Workflow
- Parse the exact claim, hypotheses, domains, and conclusion.
- State the proof plan before proving: direct proof, contradiction, induction, fixed point, comparative statics, counterexample search, or case split.
- Define all notation before use. Give object types and parameter domains.
- Prove one numbered step at a time. Each step must open with what it will show.
- Show intermediate algebra. Do not jump from setup to simplified result.
- Sign every derivative, inequality, monotonicity claim, and limit claim at the line where it appears.
- Handle edge cases and boundary behavior explicitly.
- Separate proved results from conjectures, examples, and numerical evidence.
- End with a short intuition paragraph when useful, then close the proof with
\square.
Proof Discipline
- Use
\triangleqfor definitions and=for equalities. - Use display math for multi-term expressions, ratios, derivatives, thresholds, and relation chains.
- Before algebra, say the goal: "It remains to show that ...".
- When differentiating a ratio, compute numerator and denominator derivatives before applying the quotient rule.
- When manipulating inequalities, state why the inequality direction is preserved or reversed.
- If a threshold is integer-valued but differentiated as continuous, flag the relaxation and explain how discreteness affects the claim.
- When invoking a theorem, instantiate it in the paper's notation. If the theorem is not standard, cite it precisely or prove the needed lemma.
- Never prove the general case by checking examples. Examples are evidence, not proof.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 82 lines · 64 tokens per session scan A bcbef5f11a5b
math-proof is a skill published in the GitHub repository morankor/theorist-toolbox (69 stars, last pushed 27d ago), licensed MIT. It adds 64 tokens to every session and 696 once invoked, about $0.0003 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 skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…