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 monoes/monomind --skill mastermind-executegit clone --depth 1 https://github.com/monoes/monomindWrote 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/monoes/monomind/mastermind-execute)<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-execute"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-execute/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/monoes/monomind/mastermind-execute"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-execute.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.00032 | $0.01509 |
| Opus 5.5 | $0.00013 | $0.00604 |
| Sonnet 5.5 | $0.00006 | $0.00302 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
mastermind-execute 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind Execute
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the mastermind:execute skill to implement this plan."
Note: This skill works best with subagent support (Claude Code). When subagents are available, dispatch one subagent per independent task in a single message.
Inputs
brain_context: BRAIN CONTEXT block (injected by master, or loaded standalone via mastermind-protocol/SKILL.md brain load)plan_path: path to the plan file to executeproject_name: monotask space nameboard_id: monotask board IDmode: auto | confirm
The Process
Step 1: Load and Review Plan
- Read the plan file at
plan_path - Review critically — identify any questions or concerns:
- Missing dependencies or prerequisites
- Ambiguous instructions
- Steps that contradict each other
- Verifications that cannot be run
- If concerns exist: raise them with the user before starting
- If no concerns: create a TodoWrite with each task and proceed
Step 2: Execute Tasks
For each task in the plan:
- Mark as
in_progress - Follow each step exactly — the plan has bite-sized steps; do not skip or reorder
- Run verifications as specified in the plan
- Mark as
completed
Dispatching subagents (when available): when independent tasks can run in parallel, dispatch one subagent per task in a single message via the Task tool. Each subagent starts with no memory of this session — embed the plan step and the brain_context received in Inputs directly in its prompt so it has the same grounding this skill was given.
CRITICAL — variable substitution required: before constructing the Task prompt, replace ${brain_context} and ${project_name} below with their actual literal values (the BRAIN CONTEXT block from Inputs, and the project name) — an unsubstituted ${brain_context} placeholder means the subagent executes blind to prior decisions and constraints. This is the same substitution discipline mastermind-idea/SKILL.md uses for its Task prompts.
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 · 160 lines · 32 tokens per session scan A e7a84e349b13
mastermind-execute is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 32 tokens to every session and 1,509 once invoked, about $0.0001 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-26.
Other skills, from other repositories
agent-swarm-issue
Agent skill for swarm-issue - invoke with $agent-swarm-issue.
agent-user-tools
Agent skill for user-tools - invoke with $agent-user-tools.
queue-handoff
Use when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the ball, not by going…
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.
verify-witness
Verify the Ed25519 witness manifest of a scaffolded harness. Fast yes/no signature check that proves the publisher signed this exact file set — separate from the full release-readiness umbrella in validate-harness.