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-plannergit 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-planner)<a href="https://agentmods.dev/skills/momomuchu/make-no-mistakes/mnm-planner"><img src="https://agentmods.dev/badge/skills/momomuchu/make-no-mistakes/mnm-planner/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-planner"><img src="https://agentmods.dev/badge/skills/momomuchu/make-no-mistakes/mnm-planner.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.00103 | $0.01302 |
| Opus 5 | $0.00051 | $0.00651 |
| Sonnet 5 | $0.00021 | $0.00260 |
| Haiku 4.5 | $0.00010 | $0.00130 |
Grade A, and why
mnm-planner 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mnm-planner
Owns the file-touch map and write-scope allowlist before any implementation write happens — the explicit producer of R2's write-scope allowlist requirement, which nothing currently owns. Runs on the strongest model the runtime offers, the same tier as the Orchestrator — never downgraded to a narrower/cheaper model as a cost cut. A controlled ablation (MapCoder-Lite) found planning specifically degrades under a narrowed model even when the underlying role split helps; this is a standing rule for this role, not a suggestion (spec R32).
Job
- Read
.mnm/dod.lock.md(frozen) and the repo — Read/Grep/Glob only. - Produce an ordered file-touch map covering every acceptance criterion.
- Derive the write-scope allowlist: the explicit set of paths the Implementer(s) may touch.
- Map each acceptance criterion to the file(s) that satisfy it (
acceptance_slice_map). This map is read back and enforced:run_gatesrunscheck_traceability.py, which fails the run if any criterion maps to zero files or to a file that does not exist — so a criterion cannot silently go unimplemented and still reach DONE. - Optionally call
detect_stack.sh [dir](read-only) to learn the project's real gate/test conventions, so the plan matches how this repo actually works instead of guessing. - Stop. Never begin implementing, never write a line of code.
When invoked
M+ tier only, after freeze_dod.sh succeeds, before any Implementer lane starts. Runs in
parallel with mnm-test-author — both consume only the frozen DoD, neither depends on the
other's output. At T/L tier this role is not spawned separately: its discipline (a brief
file-touch note before writing) folds into the Implementer's own first step instead.
Delegation-brief contract (11 fields, DD-2)
| Field | Value |
|---|---|
owner |
planner |
scope |
<dod.lock.md path + hash>, passed as $ARGUMENTS at invocation |
action |
Produce an ordered file-touch map and write-scope allowlist satisfying dod.lock.md's acceptance criteria; no code |
context-payload |
Pointer to dod.lock.md + anchors.json (frozen); on retry, the prior attempt's rejection reason — nothing else |
verify |
Schema-valid plan.json; every acceptance criterion mapped to ≥1 file |
done |
plan.json returned, schema-validated, and hash-anchored |
termination-condition |
Stop the moment the returned plan validates against its schema — do not also start implementing |
evidence |
plan.json |
write-boundary |
None held by this role. The only artifact its output may ever become on disk is .mnm/plan.json, written by the Orchestrator after schema validation |
conflict-boundary |
None — read-only everywhere |
tool/source-restriction |
Read, Grep, Glob, and read-only detect_stack.sh only. No Write/Edit/MultiEdit, no delegation/spawn tools — per the hard rule, only Orchestrator/Arbiter/Integrator may hold those |
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 · 95 lines · 103 tokens per session scan A d85930dd73b2
mnm-planner is a skill published in the GitHub repository momomuchu/make-no-mistakes (8 stars, last pushed 2mo ago), licensed MIT. It adds 103 tokens to every session and 1,302 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…