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 agentmods add skills/xcrft/mastermind/mastermind-design-intakenpx skills add xcrft/mastermind --skill mastermind-design-intakegit clone --depth 1 https://github.com/xcrft/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/xcrft/mastermind/mastermind-design-intake)<a href="https://agentmods.dev/skills/xcrft/mastermind/mastermind-design-intake"><img src="https://agentmods.dev/badge/skills/xcrft/mastermind/mastermind-design-intake.svg" alt="Measured on agentmods" 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 | $0.00063 | $0.00986 |
| Opus 5 | $0.00032 | $0.00493 |
| Sonnet 5 | $0.00013 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
mastermind-design-intake 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 5d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind design intake
"Make it look like the design" cannot be verified by anything. Not by a test, not by the codegraph, not by a reviewer six weeks later. A design handoff has to be converted into names before it becomes acceptance criteria, or the contract is decorative.
This is a planning step. It produces the contract; it does not implement it.
Name the source
Record the exact design source in the spec: file key and node id, or the frame URL. A spec that says "per the mockup" is unauditable — nobody can re-derive what was asked, and a design that moved on cannot be distinguished from an implementation that drifted.
If no stable reference exists, say so in the contract rather than pretending there is one.
Resolve components before writing criteria
A design tool that carries a code mapping states which repository components a
design already corresponds to. Read it, then confirm each mapped name against
the repository itself with mmcg_search — a mapping can name a component that
was since renamed or deleted.
A design element missing from the mapping does not mean the component is
missing from the codebase. Coverage is usually partial, and treating an
unmapped element as "new" is exactly how a fourth Button gets written. Fall
back to [[mastermind-component-research]] for anything unmapped, and record what
you searched.
The output of this step is a list of component names the implementation must use, each confirmed to exist.
Resolve tokens before writing criteria
Pull the design variables — colours, spacing, typography, radii — and carry
token names into the contract, never the resolved values. --color-danger
is checkable against the diff; #e5484d is a number that will drift the moment
the palette changes, and a reviewer cannot tell an intentional value from a
hardcoded one.
Where the design uses a value with no token behind it, that is a finding for the design system, not something to hardcode silently. Say which it is.
Write criteria that can fail
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.
- 5d ago First seen · 113 lines · 63 tokens per session scan A 45a8444fdeac
mastermind-design-intake is a skill published in the GitHub repository xcrft/mastermind (11 stars, last pushed 5d ago), licensed MIT. It adds 63 tokens to every session and 986 once invoked, about $0.0003 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-30.
Other skills, from other repositories
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
orchestrate
Tree-aware multi-agent GitHub-issue pool. Conductor manages task-tree from task-splitting-evaluation, executing depth-first per branch while parallelizing roots/orphans. Each worker agent owns its subtree lifecycle. Conductor tracks state (pending/started/in-progress/completed/halted) in GitHub +…
bonsai-ninja
Use bonsai-ninja as compiler-backed structural evidence when mapping a codebase, finding symbols, tracing behavior, inspecting dataflow, debugging across files, reviewing change impact, exporting graph facts, or running SAST.
task-splitting-evaluation
Recursive pre-implementation GitHub task splitting and evaluation flow. Use when the user wants Claude agents to evaluate unhandled tasks, skip already-processed tasks, mark easy leaves with detailed executor-ready comments, split broad tasks into GitHub subtasks, and keep recursing until every leaf is well described…
gh-task
Run a GitHub issue end-to-end in this repository using the committed isolated-worktree workflow. Use when the user invokes $gh-task, asks to run a GitHub task, or provides a GitHub issue number.
stacklit-navigator
Use stacklit.json to navigate codebases without burning tokens on file exploration.