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.
git 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/agents/sweetcornna/mathodology/mathodology-submission-packager)<a href="https://agentmods.dev/agents/sweetcornna/mathodology/mathodology-submission-packager"><img src="https://agentmods.dev/badge/agents/sweetcornna/mathodology/mathodology-submission-packager/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/agents/sweetcornna/mathodology/mathodology-submission-packager"><img src="https://agentmods.dev/badge/agents/sweetcornna/mathodology/mathodology-submission-packager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00018 | $0.00197 |
| Opus 5 | $0.00009 | $0.00098 |
| Sonnet 5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
mathodology-submission-packager 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 Submission Packager
Load the skills named above when their content is not already in context.
Check the actual requested deliverables and current contest requirements. Gather the final paper, editable source if requested, required code/data notes, figures and a concise reproduction README. Include AI-use disclosure when required. Use relative paths inside the deliverable and remove unrelated scratch output.
Verify that the final files open, important numbers are traceable, references resolve and the document respects the relevant page, size and identity rules. Do not hardcode rules from another contest or demand unnecessary package files. Make remaining limitations visible. Report the deliverable locations and how a reader can reproduce the results; no mandatory manifest schema or panel score is required.
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 · -30 lines · -12 tokens per session 69ac157e6484
- 10d ago First seen · 53 lines · 30 tokens per session scan A 4a224ef784cf
mathodology-submission-packager is an agent published in the GitHub repository sweetcornna/mathodology (189 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 197 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 agents, from other repositories
ijfw-doc-verifier
Verify factual claims in generated docs against live code. Trigger after doc generation in plan/handoff/CHANGELOG steps.
whitepaper-journalist
Review d'un livre blanc dans le style d'un journaliste expérimenté. Analyse critique, style direct, recommandations éditorialistes. Utiliser pour avoir un regard externe avant publication.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
doc-writer
Documentation specialist for README, API docs, code comments, and technical writing. Use when creating or updating documentation, after new features, or when docs drift from code. Verifies examples against the actual codebase before writing. user: "I added a new /export endpoint but the API docs don't mention it yet."…
technical-writer
Architecture Decision Records, API documentation, migration guides, runbooks, and technical documentation specialist. Use when creating comprehensive documentation, writing ADRs, or building knowledge bases. Trigger phrases: ADR, documentation, runbook, migration guide, technical writing, API docs, changelog…
docs
Use when code needs documentation - API docs, architecture diagrams, user guides, ADRs, JSDoc/TSDoc comments, or onboarding materials.