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-skill-authoringgit 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-skill-authoring)<a href="https://agentmods.dev/skills/sweetcornna/mathodology/mathodology-skill-authoring"><img src="https://agentmods.dev/badge/skills/sweetcornna/mathodology/mathodology-skill-authoring/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-skill-authoring"><img src="https://agentmods.dev/badge/skills/sweetcornna/mathodology/mathodology-skill-authoring.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.00023 | $0.00329 |
| Opus 5 | $0.00012 | $0.00164 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
mathodology-skill-authoring 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.
What it actually says
Mathodology Skill Authoring
Write reusable guidance around decisions, evidence and useful outputs. Explain when a method helps, how to recognize failure and when a simpler approach is better. Avoid mandatory phases, handoff schemas, arbitrary scores and prose that merely repeats another skill. Link the owning skill instead.
Every skill has SKILL.md frontmatter with a name equal to its directory and
a trigger-focused description starting with Use when. Its agents/openai.yaml
contains display_name, short_description and a default_prompt mentioning the
matching $skill-name. These metadata files are discovery interfaces, not a
workflow engine. Use concise role definitions; inherit the host's model choice.
Put detailed figure recipes, source provenance and examples in references or examples directories within the owning skill. Keep the entry point short and load only the references relevant to the task. Preserve third-party licensing; never execute downloaded source snapshots as an installation step.
Small scripts are appropriate when they perform concrete work such as plotting, backup or rendering. Keep them optional, declare dependencies, and verify the behavior they actually promise. Do not create a framework to enforce prompts.
Update all affected entry points, role skill lists, metadata and English/Chinese documentation. Keep each language natural; heading or code-block counts need not match. Check that commands, capabilities and links agree. Use maintenance for mechanical checks.
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 Changed · -89 lines · -13 tokens per session 3fea84c4e6d9
- 10d ago First seen · 121 lines · 36 tokens per session scan A d87ccecf5054
mathodology-skill-authoring is a skill published in the GitHub repository sweetcornna/mathodology (202 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 329 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-30.
Other skills, from other repositories
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…