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 mehrad-dm/mastermind --skill routegit clone --depth 1 https://github.com/mehrad-dm/mastermindWrote 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/mehrad-dm/mastermind/route)<a href="https://agentmods.dev/skills/mehrad-dm/mastermind/route"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/route/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/mehrad-dm/mastermind/route"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/route.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.00050 | $0.01265 |
| Opus 5.5 | $0.00020 | $0.00506 |
| Sonnet 5.5 | $0.00010 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
route 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 15d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MasterMind: Wayfinder
The front door of substantive work: decide what to load before you start, so you pull the 1–2 things a
task needs instead of reading the whole brain. It's the skill that operationalizes MasterMind's
token economy (~/.mastermind/engineering/active-field.md): and it knows when not to run.
Method
- Name the destination. One line: what is this task actually producing? Scope before routing.
- Right-size the map. If it's a one-line diff, a typo, or obviously covered by what's already in
context: say "no map needed, just do it" and exit. Ceremony on a trivial task is waste (this is
the same instinct as
~/.mastermind/engineering/core/rigor.md's refuse-list and "keep the always-on layer tiny"). - Detect the field:
package.json/configs/file types (usually free and decisive). - Build the load manifest: links only, no summaries. Consult
~/.mastermind/engineering/ROUTER.mdand pick, by matching the task to each node'sroute_when:- which field-pack file(s) to load (and their token cost: budget it),
- which skill(s) fit: pick from the index at
~/.mastermind/skills/README.md(which also names the isolated-context agents in~/.mastermind/agents/): read that index, since memory goes stale, - which core docs the task genuinely needs (
mindset/principles/rigor/agent-loop/product-sensein~/.mastermind/engineering/core/), - which codebase areas to read first. The manifest points to files to open; it links instead of paraphrasing (so it can't drift out of sync).
- Load progressively. For a big/foggy task, load the entrance set only; name the next files after the first decisions resolve. Front-load only the context this step uses.
Offer what fits: at most once, and only when it changes the outcome
Most users know three or four skills and never discover the rest, so a capability they already own stays invisible until it's too late to help. Routing is the one moment you can see the whole task and the whole library, so it's the right place: and the only place: to say something.
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.
- 15d ago Changed 7ed8b7398a03
- 1mo ago First seen · 81 lines · 50 tokens per session scan A 5089010b04e9
route is a skill published in the GitHub repository mehrad-dm/mastermind (23 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 1,265 once invoked, about $0.0002 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
st-full-workflow
Use when the user asks to run the complete end-to-end Strikethroo workflow for a work order in one shot in this repository — triggers include full workflow, end-to-end, plan and execute, do everything, run the whole strikethroo workflow. Do not use when the user wants only one stage (create a plan, generate tasks, or…
code-sec-review
Static security review that hunts exploitable vulnerabilities, prioritizing unauthenticated and cross-tenant attack paths.
agent-decision
Deterministic self-evaluation rubric for decision escalations — scored every run using the FRAME framework.
code-quality-review
Reviews code and plans against the project's coding rules.
review-loop
Two-mode review loop — single reviewer per epic, three reviewers for full branch.
setup-new-acpx-key
Configure the API key (or other credential) for a registered ACPX agentid (claude/codex/cursor/gemini/qwen/copilot/pi/droid/iflow/kilocode/kimi/kiro/opencode/tlamatini) end-to-end across data.keys, config.json (top-level + acpx.agents. .env), regensecrets.py, and verification via acpdoctor.