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/leventilo/mobius/claim-extractornpx skills add leventilo/mobius --skill claim-extractorgit clone --depth 1 https://github.com/leventilo/mobiusWhat 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.00028 | $0.01112 |
| Opus 5 | $0.00014 | $0.00556 |
| Sonnet 5 | $0.00006 | $0.00222 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
claim-extractor 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claim-extractor
Purpose and scope
This skill walks the paper body, the figure captions, and the surrounding
context of every equation, and returns a list of paper-anchored numerical
claims that downstream skills (simspec-author, science-integrity,
paper-diff) can compare against simulation telemetry.
The skill does NOT extract equations (that is paper-parser), does not
classify regimes (physics-interpreter), and does not generate code
(primitive-generator). It is a typed-extract stage: paper-parser artifacts
in, validated numerical_claims[] out, every claim traceable to a verbatim
source quote.
Input
The skill expects two artifacts on disk in the current working directory:
paper.jsonfrompaper-parser— the full structured paper record withequations[],figures[], body text, and the paper-level metadata.text_body.json(optional) — the segmented paper body keyed by section anchor. When absent, the skill readspaper.jsonbody text inline.
Algorithm
- Concatenate body text (skipping References / Bibliography), all figure captions, and the surrounding context of every equation.
- Chunk into ~4000-token segments with 500-token overlap.
- For each chunk, call Opus 4.7 with a strict extraction prompt (no formula symbols, no page numbers, no years).
- Merge chunk results, deduplicate by
(value, unit_ucum, source_quote[:50]). - Normalize units via Pint loaded with UCUM-compatible definitions. When a unit cannot be parsed, keep the raw string and lower the confidence.
- Assign a stable
idto every claim (snake-case derived from the symbol or the description; collisions resolved with a numeric suffix).
Output format (mandatory)
You MUST emit your final output as a single fenced json block at the END of your reply, with NO prose after the closing fence. The orchestrator parses that block by regex (`/(?:json)?\s*\n([\s\S]?)\n\s```/`) and ignores
everything else in your text content.
The canonical artifact for claim-extractor (consumed downstream as
ClaimsJson in server/src/types.ts):
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 · 116 lines · 28 tokens per session scan A 14d47d04e250
claim-extractor is a skill published in the GitHub repository leventilo/mobius (9 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 1,112 once invoked, about $0.0001 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
biopython
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use…
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…
flux-analyzer
Analyse FBA flux distributions to extract biological insights. Covers gene essentiality, phenotypic phase planes, flux sampling, pathway-level aggregation, secretion product prediction, and production of publication- quality figures.
evaluating-with-leakage-gates
Evaluate an OpenMed de-identification or clinical NER model against the leakage-first release gates G1a through G8, which gate releases on residual PHI leakage rather than on F1. Use when the user wants to run the OpenMed eval harness on a synthetic golden set, decide whether a de-id model is RELEASABLE or…
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…
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.