mathodology-workbench

mathodology-workbench is a skill for Claude Code, Codex from sweetcornna/mathodology. It costs 42 tokens per session (1,592 once invoked), scanned A, original, MIT.

A workbench for experiments and contest or research projects that connects problem definitions, code runs, results, figures, and papers. It records experiment details and checks whether results, images, and paper numbers still match the code that produced them.

In plain words
What is it for?
Use it to run experiments, validate result files, generate or check figures, and synchronise results into LaTeX or Markdown papers.
Why use it?
It reduces mismatched numbers and stale figures between experiments and published documents. It also keeps a record of inputs, outputs, seeds, commands, and validation results.

Skill for Claude CodeCodex

Written for Claude Code and Codex: installed under .claude/, but also agents/openai.yaml present. Also seen: reads .claude/ paths; mentions Claude Code; mentions Codex.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 .claude/skills/mathodology-workbench/scripts/mtd.py run --seed 1 -- python code/q1.py.

Good fit Use it to run experiments, validate result files, generate or check figures, and synchronise results into LaTeX or Markdown papers.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/sweetcornna/mathodology
agentmods
npx agentmods add skills/sweetcornna/mathodology/mathodology-workbench

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 mathodology-workbench

README.md
[![agentmods](https://agentmods.dev/badge/skills/sweetcornna/mathodology/mathodology-workbench/github.svg)](https://agentmods.dev/skills/sweetcornna/mathodology/mathodology-workbench)
Your own site
<a href="https://agentmods.dev/skills/sweetcornna/mathodology/mathodology-workbench"><img src="https://agentmods.dev/badge/skills/sweetcornna/mathodology/mathodology-workbench/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 mathodology-workbench

Your own site · 80×15
<a href="https://agentmods.dev/skills/sweetcornna/mathodology/mathodology-workbench"><img src="https://agentmods.dev/badge/skills/sweetcornna/mathodology/mathodology-workbench.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,592 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.00042 $0.01592
Opus 5.5 $0.00017 $0.00637
Sonnet 5.5 $0.00008 $0.00318
Haiku 4.5 $0.00004 $0.00159

Measured yesterday against content hash 1b88d4ebffb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mathodology-workbench 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 yesterday.

The scan reads SKILL.md. This mod also ships 17 executable files (scripts/mtd.py, scripts/test_mtd.py, scripts/workbench/__init__.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.

.claude/skills/mathodology-workbench/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mathodology Workbench

The other skills guide judgment; this one executes. scripts/mtd.py (Python 3.9+, standard library only) links the five stages of a contest through files, so each stage reads what the previous one actually produced:

Stage Produces Executable support
Problem brief problem/questions.json: per question, deliverables, metrics, inputs, assumptions, dependencies mtd.py brief lists the numbered questions; you fill in the rest
Experiments code under code/, a recorded run per execution mtd.py run -- python code/q1.py logs command, seed, inputs, outputs, exit code; placeholder scripts and stub functions are flagged
Results results/*.json in the contract below, written by code validation, provenance and staleness against the code that produced them
Figures images drawn by scripts that read results traces script → data → image; flags stale, missing, corrupt or low-resolution figures
Paper LaTeX citing \res{q1.rmse}, or Markdown citing {{res:q1.rmse}} mtd.py sync writes paper/results.tex and booktabs tables in paper/tables/; checks numbers, refs, cites, figures and the compile log, and math and citations in Markdown

Run it from the workspace (or pass --root); the path below is relative to a project with the skill installed:

python3 .claude/skills/mathodology-workbench/scripts/mtd.py init --paper-template   # or --paper-template cumcm
python3 .claude/skills/mathodology-workbench/scripts/mtd.py brief          # after the statement is in problem/
python3 .claude/skills/mathodology-workbench/scripts/mtd.py run --seed 1 -- python code/q1.py
python3 .claude/skills/mathodology-workbench/scripts/mtd.py status        # every stage; --json for tools
python3 .claude/skills/mathodology-workbench/scripts/mtd.py check --compile   # exit 1 on errors

A workspace is a folder with .mathodology/, or with problem/ and paper/ as Mathodology Studio creates them. Contracts and every check are described in references/contracts.md.

--paper-template NAME starts from a contest skeleton instead of the generic one: cumcm, mcm, stats, huawei, mathorcup or apmcm. It also sets "contest" in .mathodology/config.json, so check adds the format rules that were read in that contest's official text: no table of contents for CUMCM, the 25-page limit for MCM/ICM, anonymity. The skeletons and checks record the rules as of the date in references/contest-formats.md. The current official rules always take precedence. For 华为杯, MathorCup and APMCM the format rules were not verified, so the skeleton only organizes content.

Choose the template from the problem statement and the user's words: the contest name, the year, the problem letter and the submission instructions usually settle it. Say which contest you chose before running init. Ask the user, with the agent's question tool when it has one, when the evidence is unclear or points to a contest without a skeleton (华数杯 and others take generic), and before relying on a skeleton whose rules are unverified. When "contest" is already set, for example by Mathodology Studio's new-project dialog, keep it unless the user says otherwise. init never replaces an existing paper/main.tex.

Read the full file on GitHub · 106 lines

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. yesterday Changed · +19 lines 1b88d4ebffb8
  2. 9d ago First seen · 87 lines · 42 tokens per session scan A d0889031ec1c

Subscribe to this mod's changes

mathodology-workbench is a skill published in the GitHub repository sweetcornna/mathodology (320 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,592 once invoked, about $0.0002 per session on Opus 5.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-10-29.

Related

mathodology-workbench compared with skills from other repositories

mathodology-workbench next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
mathodology-workbenchsweetcornna/mathodologySkill320yesterdayMITA42Claude Code, Codex
semantic-scholar-deepCodeAlive-AI/ai-driven-developmentSkill167yesterdayMITA163Claude Code
fortranMindrally/skillsSkill29729d agoApache-2.0A95Claude Code
juliaMindrally/skillsSkill29729d agoApache-2.0A22Claude Code
deep-learning-pytorchMindrally/skillsSkill29729d agoApache-2.0A33Claude Code
nlp-natural-language-processingMindrally/skillsSkill29729d agoApache-2.0A28Claude Code
numpy-best-practicesMindrally/skillsSkill29729d agoApache-2.0A22Claude Code