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 blueprintgit 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/blueprint)<a href="https://agentmods.dev/skills/mehrad-dm/mastermind/blueprint"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/blueprint/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/blueprint"><img src="https://agentmods.dev/badge/skills/mehrad-dm/mastermind/blueprint.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.00098 | $0.01048 |
| Opus 5.5 | $0.00039 | $0.00419 |
| Sonnet 5.5 | $0.00020 | $0.00210 |
| Haiku 4.5 | $0.00010 | $0.00105 |
Grade A, and why
blueprint 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MasterMind: Blueprint
The plan turns the spec's what into a how that can be checked against the constitution before a
line is written. Layout and IDs: ~/.mastermind/engineering/core/spec-driven.md. Input: $ARGUMENTS.
Before planning
- Find the feature folder and read
spec.mdin full, plusspecs/constitution.md,specs/tech.md, and the active field'sstack-defaults.mdwhen a field pack exists. - Refuse to plan over open questions. If
[NEEDS CLARIFICATION]markers remain, runinterviewfirst. When the user insists on skipping, proceed and record the open markers as risks inplan.md. - Run the constitution gate. For each principle, write
pass,n/aorviolatesin the plan's gate table. A violation stops the plan until the user accepts it in the complexity table.
Plan
Write plan.md from specs/.templates/plan.md if present, else template.md. Then:
- Technical context. Language, dependencies, storage, testing, platform, performance and scale
targets. Each value comes from
tech.md, the code, or a decision you make in step 2. - Research the unknowns. One entry in
research.mdper real decision: chosen, why, rejected and why. Read the primary source for anything version-sensitive (learn). Library choices with real adoption risk go to thetech-scoutagent. - Design. Dispatch the
architectagent with the spec, the constitution andtech.md. Its output becomes the plan's design section. Keep the boundaries, data model, contracts and the reason for each. Where no isolated agent exists, followarchitect's method yourself and say so in the plan. - Write what the design implies, each only when it has content:
data-model.md: entities with fields, validation rules taken from the spec, relationships, state changes.contracts/: every interface another system or user depends on, in the form the project already uses, or a plain table when it has none.quickstart.md: the runnable steps that prove the feature works end to end, with expected output. A short script is allowed when steps alone cannot drive it.
- Name the real paths. The structure section lists the actual directories and files to create or change in this repository. Never a generic layout.
- Name what the spec implies but never says. A reasonable user expects some inputs handled that no
requirement and no edge case names. List up to five of them, such as an empty name, a double submit or a
timezone at midnight. Add each to the plan's risks and give it a task in
breakdown. A spec's silence is not permission to crash. - Re-run the gate against the finished design. Set the spec's status to
planned.
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 · 65 lines · 98 tokens per session scan A a21c90063ad1
blueprint is a skill published in the GitHub repository mehrad-dm/mastermind (23 stars, last pushed 6d ago), licensed MIT. It adds 98 tokens to every session and 1,048 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.