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-tree-controlgit 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-tree-control)<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.
<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>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.00034 | $0.02021 |
| Opus 5.5 | $0.00014 | $0.00808 |
| Sonnet 5.5 | $0.00007 | $0.00404 |
| Haiku 4.5 | $0.00003 | $0.00202 |
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.
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 | cancelreason: 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:
- Productive work continues. Only hold what genuinely needs to stop; don't block productive branches.
- Only real blockers stop work. A hold is a deliberate decision, not a pseudo-stop.
- 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
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 · 252 lines · 34 tokens per session scan A d9feb4499540
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.
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.