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 momomuchu/make-no-mistakes --skill mnm-integratorgit clone --depth 1 https://github.com/momomuchu/make-no-mistakesWrote 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/momomuchu/make-no-mistakes/mnm-integrator)<a href="https://agentmods.dev/skills/momomuchu/make-no-mistakes/mnm-integrator"><img src="https://agentmods.dev/badge/skills/momomuchu/make-no-mistakes/mnm-integrator/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/momomuchu/make-no-mistakes/mnm-integrator"><img src="https://agentmods.dev/badge/skills/momomuchu/make-no-mistakes/mnm-integrator.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.00106 | $0.01373 |
| Opus 5 | $0.00053 | $0.00687 |
| Sonnet 5 | $0.00021 | $0.00275 |
| Haiku 4.5 | $0.00011 | $0.00137 |
Grade A, and why
mnm-integrator 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 11d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mnm-integrator
Owns reconciliation when a tournament's winner could be measurably better by grafting in one specific, panel-cited improvement from a losing candidate — the previously-unowned step in "best ideas from runners-up grafted": by whom, verified how, was never answered before this role existed.
Job
- Confirm the gate that justifies running at all: a tournament ran, the arbiter declared a winner, and the panel's own citations (already required to name file:line) point to ≥1 specific way a losing candidate handled something the winner didn't. No citation → do not run; the winner ships as-is.
- Read the frozen
dod.lock.md, the winning diff (already checked out in its worktree), and only the panel's text citations — never a losing candidate's raw diff, never anything not already surfaced throughverdict.log. - Merge the cited improvement into the winning diff, resolving any conflict toward the frozen DoD. Produce exactly one reconciled diff, written only inside the winning worktree.
- Re-run the full gate stack (
run_gates.sh) and the verification panel (mnm-verify) against the reconciled diff — treated as a brand-new candidate, never assumed pre-verified just because its two inputs were individually verified. (Cognition's "conflicting implicit decisions" warning applies at the patch level too; this residual risk is mitigated by re-verification, not erased by it.) - Log the grafting event with unusual prominence in
verdict.log— not folded into a routine row. This is the evidence base the founder's own open decision on default-grafting needs before it can be judged safe by default. - Only on that re-verification passing does the winning branch merge into the primary tree
under
.mnm/lock. Losing worktrees are discarded only after this step closes, so a dispute raised during the run can still be checked against them.
When invoked
H/C tier only, tournament sub-procedure only, gated on an actual panel citation (step 1 above).
Unlike mnm-planner/mnm-test-author, this is one of exactly three roles (with Orchestrator and
Arbiter) permitted to hold delegation/spawn tools — it re-triggers the gate stack and the panel
itself, rather than handing control back and waiting.
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.
- 11d ago First seen · 98 lines · 106 tokens per session scan A 523d00bdd773
mnm-integrator is a skill published in the GitHub repository momomuchu/make-no-mistakes (8 stars, last pushed 2mo ago), licensed MIT. It adds 106 tokens to every session and 1,373 once invoked, about $0.0005 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
sunset-review
Use this skill when the user wants to identify unused, near-zero-use, or stale skills/agents/commands in the plugin surface so they can be demoted or retired. Combines agent-dispatch telemetry (start-events only) with static reference scanning, classifies every surface item into Active / Investigate / Demote / Retire…
autopilot
Use this skill when running an autonomous session-orchestration loop. Chains session-start → session-plan → wave-executor → session-end for N iterations with all 10 kill-switches (SPIRAL, FAILED wave, carryover > 50%, max-hours, max-sessions, resource-overload, token-budget, stall-timeout, sub-threshold confidence…
claude-md-drift-check
Use when detecting drift between CLAUDE.md (or AGENTS.md, the Codex CLI alias) / meta narrative and live repository state. Ten checks: absolute-path resolution, 01-projects/ count claims, issue-reference freshness, session-file existence, command-count sync, session-config-parity (mandatory template keys = error…
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
evolve
Use this skill when extracting session patterns into reusable learnings. Three modes: analyze (extract from session history), review (edit/manage existing learnings), list (display active learnings). Manages .orchestrator/metrics/learnings.jsonl.
frontmatter-guard
Injects the canonical vault frontmatter schema snippet into agent prompts before any vault-write task, preventing malformed YAML frontmatter in Obsidian notes. Context: wave-executor is about to dispatch a vault-mirror agent that writes learning notes under /Projects/vault/40-learnings/. user: "dispatch vault-write…