mastermind-delegation

mastermind-delegation is a skill for Claude Code, Codex from monoes/monomind. It costs 25 tokens per session (660 once invoked), scanned A, original, Apache-2.0.

A capability definition that lets an agent start other agents to handle specialised subtasks. The capability can be passed on so those agents can delegate too.

In plain words
What is it for?
Use it when building prompts for spawned agents that may need to divide work into additional subtasks.
Why use it?
It gives delegated work the instructions needed to create further delegation instead of stopping at one level.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions Claude Code; installed under .agents/ (shared by several agents).

Good fit Use it when building prompts for spawned agents that may need to divide work into additional subtasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/monoes/monomind/mastermind-delegation
Install

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.

Any agent
npx skills add monoes/monomind --skill mastermind-delegation
Clone the repo
git clone --depth 1 https://github.com/monoes/monomind

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mastermind-delegation

README.md
[![agentmods](https://agentmods.dev/badge/skills/monoes/monomind/mastermind-delegation/github.svg)](https://agentmods.dev/skills/monoes/monomind/mastermind-delegation)
Your own site
<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-delegation"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-delegation/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.

agentmods 80×15 button for mastermind-delegation

Your own site · 80×15
<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-delegation"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-delegation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 660 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00660
Opus 5.5 $0.00010 $0.00264
Sonnet 5.5 $0.00005 $0.00132
Haiku 4.5 $0.00003 $0.00066

Measured 2d ago against content hash 03730a4e47df, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mastermind-delegation 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.

.agents/skills/mastermind-delegation/SKILL.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Delegation Capability

This file defines the AGENT DELEGATION CAPABILITY block that MUST be included verbatim in every Task / Agent spawn within mastermind and monomind commands.

Including it in every agent prompt makes delegation recursive: an agent can spawn sub-agents, which can spawn their own sub-agents, each with full access to the same capability.


How to use this file

When writing a Task/Agent description or prompt, paste the section below verbatim after BRAIN CONTEXT:. Do not paraphrase — paste it as-is so sub-agents receive the full capability statement.


AGENT DELEGATION CAPABILITY [paste this block into every agent prompt]

== AGENT DELEGATION CAPABILITY ==
You have full access to the Agent tool (Claude Code: Task tool) to spawn
sub-agents for any specialized subtask. This capability is recursive —
sub-agents you spawn also receive it.

To choose the subagent_type for a subtask, in this order:
  1. The prompt's [PICK] line (`[PICK] agent: <name> · skill: <invoke>`),
     unless it is clearly wrong for the subtask.
  2. mcp__monomind__pick({ task: "<subtask>", kind: "agents", top: 3 })
     -> use an agents.ranked[].name.
  3. No MCP: monomind pick -t "<subtask>" --top 3 --json | jq -r '.agents.ranked[].name'
     (local binary only, never npx).
  4. Nothing returned: coder (implementation) · tester · reviewer ·
     researcher · planner · general-purpose.
Picked names always exist on disk. Do NOT invent agent names.

WHEN to delegate:
- A subtask needs deeper expertise than your primary role
- Work can be done faster in parallel by concurrent specialists
- A subtask is outside your domain but blocks your progress

HOW to delegate:
  Agent({
    subagent_type: "Agent Name",   // a name returned by the pick
    description: "Short task label",
    prompt: `Full self-contained briefing — treat every sub-agent as cold-start.
             Include: context, scope, success criteria, and this AGENT DELEGATION
             CAPABILITY block so they can further delegate if needed.`,
    run_in_background: true   // use for parallel work
  })

RULES:
- Always pass enough context for the sub-agent to work independently
- Collect and synthesize sub-agent results before writing your final output
- Report what you delegated and what each sub-agent returned
- If a sub-agent is blocked, handle it rather than silently failing
=================================

Read the full file on GitHub · 78 lines

Changes

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.

  1. 2d ago First seen · 78 lines · 25 tokens per session scan A 03730a4e47df

Subscribe to this mod's changes

mastermind-delegation is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 660 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.

Related

Other skills, from other repositories

compare-harnesses

Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.

ruvnet/metaharness · 66 tokens

create-harness

Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a…

ruvnet/metaharness · 89 tokens

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.

ruvnet/metaharness · 85 tokens

example-harness

Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming…

ruvnet/metaharness · 90 tokens

oia-manifest

Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture. Self-describes the harness's MCP wiring, witness signing, audit log, identity posture (always 'none' at v0.1). --check verifies an existing manifest, --dry-run prints without writing, --json emits to stdout.

ruvnet/metaharness · 79 tokens

repo-genome

7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.

ruvnet/metaharness · 73 tokens