verifying-proofs

verifying-proofs is a skill for Claude Code, Codex from chgagne/claude-skills-research. It costs 88 tokens per session (6,180 once invoked), scanned A, original, MIT.

A guide for checking the mathematics inside a paper, such as theorem proofs, algebraic derivations, bounds, and lemmas. A lemma is a smaller result used to support a larger theorem.

In plain words
What is it for?
Use it to inspect proofs and derivations in paper sources, report problems step by step, and record the exact assumption or argument that needs correction.
Why use it?
It helps identify specific gaps, missing assumptions, invalid induction steps, or inconsistent restatements without confusing unclear notation with an actual mathematical error.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions subagents.

Good fit Use it to inspect proofs and derivations in paper sources, report problems step by step, and record the exact assumption or argument that needs correction.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chgagne/claude-skills-research/verifying-proofs
Install

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.

Any agent
npx skills add chgagne/claude-skills-research --skill verifying-proofs
Clone the repo
git clone --depth 1 https://github.com/chgagne/claude-skills-research

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for verifying-proofs

README.md
[![agentmods](https://agentmods.dev/badge/skills/chgagne/claude-skills-research/verifying-proofs/github.svg)](https://agentmods.dev/skills/chgagne/claude-skills-research/verifying-proofs)
Your own site
<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.

agentmods 80×15 button for verifying-proofs

Your own site · 80×15
<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>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,180 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 11d ago against content hash 9bf45ff47a8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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.

The scan reads SKILL.md. This mod also ships 28 executable files (assets/proofcheck/__init__.py, assets/proofcheck/__main__.py, assets/proofcheck/compose.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

verifying-proofs/SKILL.md · 449 lines

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 is sideconds alone, 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 to UNVERIFIED rather than to a finding
  • --claims thm:main,lem:2 — restrict to named claims
  • --emit-symbols-templaterun this first on any real paper. Writes a --symbols skeleton 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 — write proof-ledger.json and 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-written build() may produce a CRITICAL
  • Exit code 2 means degraded coverage — a checker was missing, a script was not translated, or the segmenter dropped proof text

Read the full file on GitHub · 449 lines

Files

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.

Changes

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.

  1. 11d ago First seen · 449 lines · 88 tokens per session scan A 9bf45ff47a8f

Subscribe to this mod's changes

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.

Related

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.…

kgraph57/paper-writer-skill · 106 tokens

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.…

PangenomeAI/academic-skills-food-nutrition · 154 tokens

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…

PangenomeAI/academic-skills-food-nutrition · 180 tokens

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…

PangenomeAI/academic-skills-food-nutrition · 137 tokens

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…

PangenomeAI/academic-skills-food-nutrition · 166 tokens

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…

PangenomeAI/academic-skills-food-nutrition · 218 tokens