mastermind-plan-to-tasks

mastermind-plan-to-tasks is a skill for Claude Code, Codex from monoes/monomind. It costs 32 tokens per session (2,425 once invoked), scanned A, original, Apache-2.0.

A plan-to-task converter that turns written work plans into assigned issues for a Mastermind organization, including specialties, dependencies, and parallel work.

In plain words
What is it for?
Use it to create or preview assigned issues from a plan, optionally placing them in a project or workspace.
Why use it?
It removes the manual effort of breaking a plan into issues and deciding who should handle each part.

Skill for Claude CodeCodex

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

Good fit Use it to create or preview assigned issues from a plan, optionally placing them in a project or workspace.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-plan-to-tasks"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-plan-to-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,425 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.00032 $0.02425
Opus 5.5 $0.00013 $0.00970
Sonnet 5.5 $0.00006 $0.00485
Haiku 4.5 $0.00003 $0.00243

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

Security

Grade A, and why

mastermind-plan-to-tasks 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-plan-to-tasks/SKILL.md · 245 lines

How it starts

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

Mastermind Plan to Tasks

This skill is invoked directly via /mastermind-plan-to-tasks.


Inputs

  • brain_context: BRAIN CONTEXT block (injected by command, or loaded below if standalone)
  • org_name: org to create issues in (required)
  • plan: the plan text (required — paste inline or pipe in)
  • project_id: assign all issues to this project (optional)
  • workspace_id: assign all issues to this workspace (optional)
  • dry_run: true | false (default: false — if true, print plan without creating issues)
  • caller: command | master

Step 0 — Brain Load (standalone only)

If caller is not "command", load brain context following mastermind-protocol/SKILL.md Brain Load Procedure with namespace: ops.


Step 1 — Validate Inputs

[ -z "$org_name" ] && { echo "ERROR: --org required."; exit 1; }
[ -z "$plan"     ] && { echo "ERROR: --plan required (the plan text to decompose)."; exit 1; }

orgFile=".monomind/orgs/${org_name}.json"
[ ! -f "$orgFile" ] && { echo "ERROR: Org '${org_name}' not found."; exit 1; }

Step 2 — Load Agents for Specialty Matching

echo "PLAN-TO-TASKS — $org_name"
echo "────────────────────────────────────────────────────────"
echo ""
echo "AGENTS IN ORG:"
jq -r '(.roles // [])[] | "  \(.id)  \(.title // "-")  [\(.adapter.type // "?")]"' "$orgFile"
echo ""

Step 3 — Decompose Plan into Issues

Read the plan carefully and apply these rules:

Planning principles (from Paperclip plan-to-tasks):

  1. Plan deeply. Capture real detail: goals, constraints, unknowns, success criteria, risks. A shallow plan becomes rework.
  2. Know your team. Read the org's agents and their specialties (titles, roles, adapters) before assigning anything.
  3. Assign for specialty. Hand each piece of work to the most relevant agent. If no agent fits, flag the gap.
  4. Take responsibility. When you (the AI) are best-suited for a piece, assign it to yourself instead of delegating.
  5. Use the dependency tree. Express every concrete deliverable as an issue. Wire real blockers via blockedByIssueIds. When done, dependents auto-wake.
  6. Order, then parallelize. Sequence by real dependencies. Independent branches start in parallel.
  7. Enough is enough. Plans unblock execution. Don't re-plan already clear work.

Read the full file on GitHub · 245 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 · 245 lines · 32 tokens per session scan A fb1a4e31814d

Subscribe to this mod's changes

mastermind-plan-to-tasks 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 2,425 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

agent-swarm-issue

Agent skill for swarm-issue - invoke with $agent-swarm-issue.

ruvnet/ruflo · 21 tokens

agent-user-tools

Agent skill for user-tools - invoke with $agent-user-tools.

ruvnet/ruflo · 16 tokens

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…

mvschwarz/openrig · 94 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

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.

ruvnet/metaharness · 0 tokens

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.

ruvnet/metaharness · 45 tokens