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 breakdowngit 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/breakdown)<a href="https://agentmods.dev/skills/mehrad-dm/mastermind/breakdown"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/breakdown/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/breakdown"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/breakdown.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.00092 | $0.00935 |
| Opus 5.5 | $0.00037 | $0.00374 |
| Sonnet 5.5 | $0.00018 | $0.00187 |
| Haiku 4.5 | $0.00009 | $0.00093 |
Grade A, and why
breakdown 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MasterMind: Breakdown
tasks.md is the build order: small enough that each task is checkable, ordered so each user story
ships alone. Layout and IDs: ~/.mastermind/engineering/core/spec-driven.md. Input: $ARGUMENTS.
Read first
spec.md for the stories and their priorities, plan.md for paths and structure, then data-model.md,
contracts/, research.md and quickstart.md where they exist. Use specs/.templates/tasks.md if
present, else template.md.
The task line
- [ ] T014 [P] [US1] Add the export button to src/reports/ReportHeader.tsx (US1/AC1, FR-002)
- [ ]then aT###ID in execution order. IDs are never reused or renumbered.[P]only when it touches different files from every unfinished task before it.[US#]on every task inside a story phase, and on no other.- The exact file path, and the spec IDs it serves in parentheses.
The phases
- Setup: what the project needs before anything else, such as dependencies, config and env vars.
- Foundation: what every story needs and no story can deliver alone. Keep it small; most work belongs to a story.
- One phase per user story, in priority order. Each is a vertical slice: its models, logic, interfaces and wiring, ending in a checkpoint that runs the story's independent test.
- Polish: cross-cutting work that touches several stories.
Delete a phase with no tasks. Never write a heading over "None".
Refactoring the code needs before a story can land goes first, as its own tasks in Foundation. A change
too wide for one slice, such as renaming a column every story reads, is sequenced expand, migrate,
contract (deprecate), never forced into a story.
Within a story: tests first when they are required, then data, then logic, then the surface, then the wiring that connects them.
Rules
- Tests are tasks only when required. Required means the constitution demands them, the spec asks
for them, or the user said so. Otherwise
qaverifies, and tests are offered after the build. - Quote the constraint. A field with a length limit, an enum or a validation rule from
data-model.mdhas that rule copied into its task, so it is not left to memory at build time. - Every requirement gets a task. Before writing the file, check each
FR-###and each acceptance criterion maps to at least one task. List any that do not in your report. - A task that needs "and" is two tasks. One task, one change, one way to tell it worked.
What ships with it
2 files 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 First seen · 72 lines · 92 tokens per session scan A 547199264377
breakdown is a skill published in the GitHub repository mehrad-dm/mastermind (23 stars, last pushed 6d ago), licensed MIT. It adds 92 tokens to every session and 935 once invoked, about $0.0004 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-10-08.
Other skills, from other repositories
st-execute-blueprint
Use when the user asks to run, execute, implement, or carry out a Strikethroo plan or its blueprint by plan ID in this repository — triggers include execute blueprint, run the plan, implement plan, build the plan. Do not use to create a plan, to only generate tasks, to run a single task, or for generic development…
st-generate-tasks
Use when the user asks to decompose, break down, or generate tasks for an existing Strikethroo plan ID in this repository — triggers include generate tasks, break down the plan, decompose plan, create the task blueprint. Do not use to create a new plan, to execute tasks, or for generic project planning outside…
st-create-plan
Use when the user asks to draft, scope, or write up a new Strikethroo plan for a work order, feature, or initiative in this repository — triggers include create plan, new plan, plan this, scope a plan, strikethroo plan. Do not use to decompose an existing plan into tasks, to execute a plan, or for generic…
plan-management
Plan lifecycle — grill entry point, grounding, artifact review, per-epic execution, revision.
architect-impl-grounding
Grounds the grill's settled decisions in the codebase — annotates impl.md with file paths, signatures, reference files, test specs, and LOC; re-grounds the next epic after each landing.
task-tracking
File-based to-do tracking for multi-step and multi-session work.