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 skills add chgagne/claude-skills-research --skill verifying-proofsgit clone --depth 1 https://github.com/chgagne/claude-skills-researchWrote 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/chgagne/claude-skills-research/verifying-proofs)<a href="https://agentmods.dev/skills/chgagne/claude-skills-research/verifying-proofs"><img src="https://agentmods.dev/badge/skills/chgagne/claude-skills-research/verifying-proofs/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/skills/chgagne/claude-skills-research/verifying-proofs"><img src="https://agentmods.dev/badge/skills/chgagne/claude-skills-research/verifying-proofs.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.00088 | $0.06180 |
| Opus 5 | $0.00044 | $0.03090 |
| Sonnet 5 | $0.00018 | $0.01236 |
| Haiku 4.5 | $0.00009 | $0.00618 |
Grade A, and why
verifying-proofs 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 11d 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 — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifying Proofs
Overview
A proof is refuted one step at a time, and reported one gap at a time. The useful output of this skill is rarely "the theorem is false" — it is this step needs a hypothesis nobody stated, this induction has no base case, this lemma's appendix restatement drops a condition its proof uses.
Core principle: the tool may never report its own limitations as the paper's mistakes. Every rule below exists to keep that true. A checker that says "counterexample at $x = -11/5$" about a step that plainly meant $x > 0$ has not found an error; it has taught its reader to ignore the next twenty findings.
Two consequences, both measured on real papers:
- A symbol whose domain the paper never stated can never produce a counterexample. On arXiv:1509.01240, 54 of 61 symbols had no readable domain. Sampling those freely would have produced dozens of "errors" against correct mathematics.
- The default run is a hygiene checker, not a correctness checker. Measured against six papers with documented, localised proof errors, the no-CAS engines found none of them. What they do find — a dependency cycle, an induction with no base case, a restatement that drops a hypothesis, a division by something nobody proved non-zero — is worth having, and it is not the same thing as checking whether the mathematics is right. To check correctness you must fill in check scripts, and doing so refuted a step in Adam's convergence proof exactly. See Measured results.
Run it
python3 ~/.claude/skills/verifying-proofs/assets/run-proofcheck.py main.tex \
--out review-assets/
Run it by absolute path from the paper directory. Stdlib only — no install, no venv, no dependencies. SymPy and Z3 are optional external checkers: probed at runtime, never installed, and their absence degrades the run instead of breaking it.
--engines sideconds,rational,symbolic— default issidecondsalone, which needs nothing external and produced every finding in the measurements below. Every scripted engine named gets its own script per step (checks/<step>.<engine>.py), and engines that disagree compose toUNVERIFIEDrather than to a finding--claims thm:main,lem:2— restrict to named claims--emit-symbols-template— run this first on any real paper. Writes a--symbolsskeleton for every symbol whose domain the paper never states, ordered by how many unmet side conditions each one stands in, with a sidecar naming the obligations it blocks and the legal values--symbols symbols.json—{"\\gamma": "unit-interval-half-open"}; one minute of your time unblocks more checking than any amount of inference. A value outside the known vocabulary is now refused with the nearest legal name rather than accepted and silently matching nothing--emit-stubs-only— write every check script and run nothing, so you can read what would run first--ledger-only— writeproof-ledger.jsonand stop--translations A.json,B.json— adjudicate two independent agent-authored translations of the emitted scripts. See Two translations below; this is the only route by which an agent-writtenbuild()may produce aCRITICAL- Exit code
2means degraded coverage — a checker was missing, a script was not translated, or the segmenter dropped proof text
What ships with it
32 files 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.
- assets/proofcheck/__init__.py 0 B runs code
- assets/proofcheck/__main__.py 12 KB runs code
- assets/proofcheck/compose.py 19 KB runs code
- assets/proofcheck/engines/__init__.py 1.1 KB runs code
- assets/proofcheck/engines/gradient.py 4.9 KB runs code
- assets/proofcheck/engines/rational.py 7.7 KB runs code
- assets/proofcheck/engines/smt.py 6.2 KB runs code
- assets/proofcheck/engines/symbolic.py 7.2 KB runs code
- assets/proofcheck/ledger_io.py 5.7 KB runs code
- assets/proofcheck/report.py 8.0 KB runs code
- assets/proofcheck/sandbox.py 7.3 KB runs code
- assets/proofcheck/stubs.py 15 KB runs code
- assets/proofcheck/twotrans.py 7.8 KB runs code
- assets/run-proofcheck.py 655 B runs code
- assets/tests/test_adam_refutation.py 11 KB runs code
- assets/tests/test_compose.py 20 KB runs code
- assets/tests/test_gradient_on_a_real_claim.py 7.1 KB runs code
- assets/tests/test_gradient.py 3.8 KB runs code
- assets/tests/test_rational.py 6.2 KB runs code
- assets/tests/test_report.py 7.6 KB runs code
- assets/tests/test_sandbox.py 6.0 KB runs code
- assets/tests/test_seeded_errors.py 13 KB runs code
- assets/tests/test_smt.py 5.9 KB runs code
- assets/tests/test_stdlib_only.py 3.3 KB runs code
- assets/tests/test_stubs.py 13 KB runs code
- assets/tests/test_supersession.py 7.9 KB runs code
- assets/tests/test_symbols_template.py 3.4 KB runs code
- assets/tests/test_twotrans.py 6.2 KB runs code
- reference/engines.md 5.2 KB
- reference/false-alarms.md 26 KB
- reference/step-ledger.md 5.3 KB
- reference/structural-audit.md 5.6 KB
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.
- 11d ago First seen · 449 lines · 88 tokens per session scan A 9bf45ff47a8f
verifying-proofs is a skill published in the GitHub repository chgagne/claude-skills-research (4 stars, last pushed 6d ago), licensed MIT. It adds 88 tokens to every session and 6,180 once invoked, about $0.0004 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-31.
Other skills, from other repositories
paper-writer
Medical/scientific paper writing workflow skill. Manages the full pipeline from literature search to submission-ready manuscript. Creates and manages a project directory with IMRAD-format section files, literature matrix, reference management, and quality checklists. Supports both English and Japanese papers.…
food-research
Run a comprehensive, multi-source literature and evidence-synthesis workflow for food & nutrition science. Use when the user wants to research a food/nutrition topic in depth, do a literature review, build an evidence brief, screen and synthesize many sources, verify citations, or scope a systematic review.…
food-paper
Multi-subagent manuscript system for food & nutrition science covering the whole research process: understand the field, frame research questions, curate and analyze data, run statistics, build figures and tables, construct the discussion, draft, polish, and self-review — journal-aware throughout. Includes a…
food-pipeline
Master orchestrator for the whole food & nutrition research-to-publication workflow. Coordinates the specialist skills — each with its own subagent set — into one governed path: journal selection, research (food-research / food-deep-research), writing & analysis (food-paper), figures (food-figure), peer review…
food-deep-research
General-purpose deep research that produces a fully written, source-validated literature review on any question: scope it, design the method, discover and screen sources by journal ranking, validate every source, extract and verify evidence, synthesize, stress-test, then write and format the review (APA 7.0 by…
food-figure
Comprehensive figure system for food & nutrition manuscripts: analyzes the user's data, recommends the best figure(s) to make, then produces submission-grade graphics in Python or R at the target journal's spec. Handles all common scientific figure types (bar/box/violin, line/kinetic, scatter/regression, Bland–Altman…