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/vantasnerdan/substrate-framework/theorem-synthesisnpx skills add vantasnerdan/substrate-framework --skill theorem-synthesisgit clone --depth 1 https://github.com/vantasnerdan/substrate-frameworkWhat 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 | $0.00074 | $0.01067 |
| Opus 5 | $0.00037 | $0.00534 |
| Sonnet 5 | $0.00015 | $0.00213 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
theorem-synthesis 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 2d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Theorem Synthesis
Promote a new positive statement by proving the missing glue between accepted claims. Keep proof, empirical applicability, and scientific interpretation distinct so each can advance without becoming ceremony for the others. Protect the strongest useful theorem supported by the composition; do not make a proof easier by shrinking the result to a tautology or isolated special value.
Establish the target
Read AGENTS.md, governance/releases/current.yaml, the relevant entries in
governance/claims.yaml, and .agents/skills/physics-erdos-loop/SKILL.md.
Instantiate memory-templates/theorem-synthesis.md and a synthesis proposal
manifest before substantive proof work.
State:
- one exact higher theorem;
- at least two distinct accepted dependency claims;
- the structural gap not closed by any accepted claim;
- assumptions, exclusions, and intended consumers;
coreorinterpretivelayer, with a named hypothesis for the latter.
Do not re-review accepted dependencies. Audit only that the theorem uses their exact accepted scope. There is no statement-length cap once the dependency and assumption boundary is explicit.
If the composition needs a real hypothesis, state it and use the interpretive layer rather than rejecting an otherwise useful conditional theorem. A missing bridge is “not yet proved,” not a refutation of either accepted atom.
If the scientific mechanism is genuinely open, compare plausible mechanisms
under preregistered structural criteria. If the theorem statement is fixed,
declare target_kind: fixed_theorem and proceed with one sound proof route;
do not invent rival mechanisms to satisfy a form.
Run scripts/find_synthesis_candidates.py when cross-sector graph structure can
help discovery. Treat its ranking as a hint, never as evidence or a gate.
Prove the glue
Choose the strongest practical proof backend for the exact statement:
- Use SymPy for exact identities, substitutions, eliminations, and finite symbolic chains.
- Use Lean for finite formal statements and prioritize an end-to-end theorem over disconnected attestations. Import shared framework definitions where practical, reject proof escapes, inspect the theorem and axiom footprint, and audit the map back to the physics statement.
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.
- 2d ago First seen · 109 lines · 74 tokens per session scan A 49c2b976a6ef
theorem-synthesis is a skill published in the GitHub repository vantasnerdan/substrate-framework (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,067 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
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…
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…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
mixed-precision
Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.