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 sweetcornna/mathodology --skill mathodology-dev-test-releasegit clone --depth 1 https://github.com/sweetcornna/mathodologyWrote 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/sweetcornna/mathodology/mathodology-dev-test-release)<a href="https://agentmods.dev/skills/sweetcornna/mathodology/mathodology-dev-test-release"><img src="https://agentmods.dev/badge/skills/sweetcornna/mathodology/mathodology-dev-test-release/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/sweetcornna/mathodology/mathodology-dev-test-release"><img src="https://agentmods.dev/badge/skills/sweetcornna/mathodology/mathodology-dev-test-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.00530 |
| Opus 5.5 | $0.00010 | $0.00212 |
| Sonnet 5.5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
mathodology-dev-test-release 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 today.
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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mathodology Repository Checks
Repository maintenance checks are optional utilities; they do not run during modeling by default and cannot establish mathematical or editorial quality.
From a repository checkout, run:
python3 .claude/skills/mathodology-dev-test-release/scripts/validate_repo.py all
The standard-library checker covers skill/role metadata, local Markdown links,
known skill references and allowed repository paths (skills, roles, workflows,
docs, apps/studio/ and Studio's Windows workflow). Individual commands are
metadata, links, boundary and selftest. It supports a source export without
Git; in a checkout it also inspects tracked paths. It does not enforce document
heading counts, search wording, updater contracts or contest run schemas.
The figure demonstration script and PDF overview utility have self-tests; backup can be verified by extracting the archive and checking its checksum (backup and installation guidance).
Explicitly requested releases
Release work is repository maintenance, separate from the modeling guidance.
Inspect the current remote branch, recent releases and existing tags. Choose the
next version consistently with that history and describe migration requirements
when removing an old entry point or utility. The only package manifest is
Mathodology Studio's in apps/studio/; do not add another manifest,
application build or CI pipeline for the skills pack itself.
Review the actual changes, run relevant checks and verify retained asset licenses.
Use a focused branch and pull request when that matches repository practice.
Respect branch protections; do not bypass required reviews or checks. Once the
authorized changes are merged, tag that exact commit and publish the requested
release with concise changes, migration notes and truthful validation results.
Never move an existing release tag to a different commit. Verify the published
tag and release point to the intended source. GitHub's source archives are enough
unless the user requests additional artifacts. For a Studio release, bump
apps/studio/package.json and the download links in both READMEs, build the
macOS and Linux packages with pnpm dist and pnpm dist:linux, and attach the
Windows installer from the .github/workflows/studio-windows.yml run on the
release tag (signed once SignPath is configured; each request waits for an
approver). Publish SHA-256 sums of every file.
What ships with it
2 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.
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.
- today Changed · +5 lines d04a113546f4
- yesterday Changed · -3 lines 91867fe84579
- 1mo ago Changed · -45 lines · -10 tokens per session a40d38de292f
- 1mo ago First seen · 93 lines · 36 tokens per session scan A 1d49856d7f92
mathodology-dev-test-release is a skill published in the GitHub repository sweetcornna/mathodology (313 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 530 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
release-verification
A release-verification checklist for software versions and packages. It covers changelogs, tests, packaging, installation smoke checks, version-control actions, publishing, and checks after release.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
ship
Pre-release gate — run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.