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-task-executornpx skills add xcrft/mastermind --skill mastermind-task-executorgit clone --depth 1 https://github.com/xcrft/mastermindWhat 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.00062 | $0.01423 |
| Opus 5 | $0.00031 | $0.00711 |
| Sonnet 5 | $0.00012 | $0.00285 |
| Haiku 4.5 | $0.00006 | $0.00142 |
Grade A, and why
mastermind-task-executor 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 2d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind task executor
Implement the approved outcomes in spec.md; do not reinterpret the product
request or widen Scope. Acceptance Criteria define success. Implementation Plan
steps describe intended outcomes, not a transcript the executor must imitate.
Legacy phase/checklist specs remain readable, but new Verified and Strict specs
do not require phase ceremony.
Activation boundary
Use this skill only when the caller provides an approved task path or an approved spec. Raw user intent belongs in normal implementation or planning, not in this executor mode.
The task folder may contain reports or scratch files. spec.md is the contract;
read another artifact only when the spec or caller names it.
Before editing
- Read the complete spec.
- Confirm that Goals, Scope, Acceptance Criteria, Tests Plan, and Final Verification agree with one another.
- Confirm every intended edit is authorized by
touchesor Scope. - When
~/.mastermind/style.mdexists, use relevant non-conflicting rules as preferences. Repository code, formatter/linter configuration, and the spec take precedence over the user-global profile. Deterministic code-shape observations are diagnostic evidence, not implementation instructions; do not apply a language-specific observation to another language. Commit voice is fallback-only when repository policy is silent. - For a named symbol, use mmcg to check its current location and impact. Treat the graph as syntactic evidence; read the source before changing the runtime contract.
Stop before editing when the spec is contradictory, an authorized path is missing, the structural evidence is materially stale, or the requested work would cross Scope, security, compatibility, or permission boundaries.
Implement and verify
For each Implementation Plan step, or each legacy phase:
- Implement the stated outcome inside Scope.
- Apply literal
FIND:/CHANGE TO:blocks exactly when present. A mismatch is contract drift; do not fuzzy-match it. - Otherwise follow Acceptance Criteria and surrounding project conventions.
- Run the focused verification associated with the changed behavior.
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.
- 2d ago First seen · 165 lines · 62 tokens per session scan A 2c0271534f33
mastermind-task-executor is a skill published in the GitHub repository xcrft/mastermind (11 stars, last pushed 7d ago), licensed MIT. It adds 62 tokens to every session and 1,423 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.