mastermind-tree-control

mastermind-tree-control is a skill for Claude Code, Codex from monoes/monomind. It costs 34 tokens per session (2,021 once invoked), scanned A, original, Apache-2.0.

A control tool for pausing, holding, releasing, cancelling, or previewing an issue tree. An issue tree is a root task with related work branches beneath it.

In plain words
What is it for?
Preview a control action, hold work during review, release a hold, or cancel a root issue and its affected branches.
Why use it?
It can stop runaway or blocked work while allowing unrelated productive branches to continue. It also requires a clear reason and release path for holds or cancellations.

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 Preview a control action, hold work during review, release a hold, or cancel a root issue and its affected branches.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-tree-control"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-tree-control.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,021 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.00034 $0.02021
Opus 5.5 $0.00014 $0.00808
Sonnet 5.5 $0.00007 $0.00404
Haiku 4.5 $0.00003 $0.00202

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

Security

Grade A, and why

mastermind-tree-control 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-tree-control/SKILL.md · 252 lines

How it starts

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

Mastermind Tree Control

This skill is invoked directly via /mastermind-tree-control.


Inputs

  • brain_context: BRAIN CONTEXT block (injected by command, or loaded below if standalone)
  • org_name: org to operate on (required)
  • issue_id: root issue/task ID to control (required)
  • action: preview | hold | release | cancel
  • reason: reason for the hold/cancel (required for hold/cancel)
  • caller: command | master

Three Invariants (MUST be preserved)

All tree-control actions must respect these invariants:

  1. Productive work continues. Only hold what genuinely needs to stop; don't block productive branches.
  2. Only real blockers stop work. A hold is a deliberate decision, not a pseudo-stop.
  3. No infinite loops. Release must be possible — never hold without a clear release path.

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 — Load Org and Issue

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

issuesFile=".monomind/orgs/${org_name}-issues.json"
[ ! -f "$issuesFile" ] && { echo "ERROR: No issues file found for org '${org_name}'."; exit 1; }

Step 2 — Execute Action

preview (default)

Preview what a hold/cancel would affect without making changes:

echo "TREE CONTROL PREVIEW — $org_name  root: $issue_id"
echo "════════════════════════════════════════════════════════"

python3 - "$issuesFile" "$issue_id" <<'PYEOF'
import json, sys

data   = json.load(open(sys.argv[1]))
rootId = sys.argv[2]
issues = {i["id"]: i for i in data.get("issues", [])}

root = issues.get(rootId)
if not root:
    print(f"ERROR: Issue '{rootId}' not found.")
    sys.exit(1)

print(f"  Root:   {root.get('id')} — {root.get('title','?')} [{root.get('status','?')}]")
print()

# Find subtree
def subtree(iid, depth=0):
    children = [i for i in issues.values() if i.get("parentId") == iid or iid in (i.get("blockedByIssueIds") or [])]
    for c in children:
        st = c.get("status","?")
        icon = "⚠" if st in ("in_progress","in_review") else "○"
        print(f"  {'  ' * depth}{icon} {c['id']} — {c.get('title','?')} [{st}]")
        subtree(c["id"], depth + 1)

subtree(rootId)

active = [i for i in issues.values()
          if i.get("status") in ("in_progress","in_review")
          and (i.get("parentId") == rootId or rootId in (i.get("blockedByIssueIds") or []))]
print()
print(f"  Active issues in subtree: {len(active)}")
print(f"  Holding root would affect all {len(active)} active issue(s).")
print()
print("  To hold: /mastermind-tree-control --org <org> --action hold --issue-id <id> --reason 'Review needed'")
print("  To cancel: /mastermind-tree-control --org <org> --action cancel --issue-id <id> --reason 'No longer needed'")
PYEOF

Read the full file on GitHub · 252 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 · 252 lines · 34 tokens per session scan A d9feb4499540

Subscribe to this mod's changes

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