mastermind-protocol

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

A shared set of rules for loading and saving project context, structuring results, scoring memory, and briefing delegated agents. It is a reference used by other workflow tools, not a standalone command.

In plain words
What is it for?
It helps define agent handoffs, recursive delegation, task briefs, output formats, and project memory handling.
Why use it?
It gives related agents a consistent way to pass context and instructions, reducing missing information when work moves between them.

Skill for Claude CodeCodex

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

Good fit It helps define agent handoffs, recursive delegation, task briefs, output formats, and project memory handling.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/monoes/monomind/mastermind-protocol
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-protocol
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-protocol

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-protocol"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-protocol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,648 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.00029 $0.04648
Opus 5.5 $0.00012 $0.01859
Sonnet 5.5 $0.00006 $0.00930
Haiku 4.5 $0.00003 $0.00465

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

Security

Grade A, and why

mastermind-protocol 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-protocol/SKILL.md · 298 lines

How it starts

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

Mastermind Protocol

This file is a reference loaded by mastermind domain skills and master. It is NEVER invoked directly via the Skill tool.


Agent Delegation Protocol

Every Task/Agent spawn in mastermind and monomind MUST include the AGENT DELEGATION CAPABILITY block from mastermind-delegation/SKILL.md.

This makes delegation recursive: every spawned agent can itself spawn sub-agents, which can spawn their own sub-agents. The capability block tells each agent how to pick a real agent (the [PICK] line, mcp__monomind__pick, or local monomind pick) and how to delegate.

Placement: In the Task/Agent description or prompt field, insert the full == AGENT DELEGATION CAPABILITY == ... ================================= block immediately after BRAIN CONTEXT:.

Why this matters: Agents read their prompts cold. Without the delegation block, a spawned Security Engineer won't know it can delegate codebase exploration to a reviewer, or that it can spawn a Backend Architect to fix the issues it finds. With the block, every agent in the chain can self-organize and pull in the right specialist.

Reference: Full block text is in mastermind-delegation/SKILL.md. Copy it verbatim — do not paraphrase.


Brain Load Procedure

Execute at the START of every mastermind run (master or standalone domain command). Load in this order:

Step A — Tier 3 core principles (all domains): Try mcp__monomind__memory_hierarchical-recall with query "mastermind principles", topK 20. If it returns an error, fall back to: mcp__monomind__memory_pattern-search with query "mastermind principles", namespace "mastermind:principles", limit 20. Record the entry ids of whichever call actually returned results — results[].id from memory_hierarchical-recall, or patterns[].id from the memory_pattern-search fallback — into a running list: recalled_entry_ids.

Step B — Tier 2 weekly summary for this domain: Try mcp__monomind__memory_context-synthesize with query [current prompt keywords], maxEntries 10. If it fails, fall back to: mcp__monomind__memory_pattern-search with query [current prompt keywords], namespace "mastermind:<domain>:weekly", limit 10. memory_context-synthesize returns only a context string and a sources count — no entry ids — so it cannot add to recalled_entry_ids. Only the memory_pattern-search fallback contributes ids (patterns[].id); append them to recalled_entry_ids when that fallback runs.

Read the full file on GitHub · 298 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 · 298 lines · 29 tokens per session scan A b02b9c1086fc

Subscribe to this mod's changes

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