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-releasegit 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-release)<a href="https://agentmods.dev/skills/monoes/monomind/mastermind-release"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-release/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-release"><img src="https://agentmods.dev/badge/skills/monoes/monomind/mastermind-release.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.00038 | $0.02010 |
| Opus 5.5 | $0.00015 | $0.00804 |
| Sonnet 5.5 | $0.00008 | $0.00402 |
| Haiku 4.5 | $0.00004 | $0.00201 |
Grade A, and why
mastermind-release 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mastermind Release Domain
This skill is invoked by mastermind:master or directly via /mastermind:release.
Inputs
brain_context: BRAIN CONTEXT block (injected by master, or loaded standalone via mastermind-protocol/SKILL.md brain load)prompt: the release goal (version target, scope, environment)project_name: monotask space nameboard_id: monotask board ID (set by master, or created standalone)mode: auto | confirm
Complexity Assessment
Assess the prompt to determine execution mode:
Simple (direct execution): Single-step release action:
- "Bump the version to 1.2.3 in package.json"
- "Generate a changelog for this git range" → Use a single release-manager or coder agent. Skip manager delegation.
Complex (spawn Release Manager agent): Any of these:
- Full end-to-end release (version + changelog + tests + deploy)
- Multi-environment deployment (staging → production)
- Release requiring review gates or rollback plan
- Coordinated release across multiple packages → Spawn Release Manager agent with full briefing.
Standalone Execution (when called without master)
If this skill is invoked directly (not by master):
- Load brain context following mastermind-protocol/SKILL.md Brain Load Procedure (namespace:
release) - Run intake from mastermind-intake/SKILL.md if prompt is vague
- Follow mastermind-protocol/SKILL.md Monotask Space+Board Setup Procedure:
project_name="${project_name:-$(basename "$PWD")}" space_id=$(monotask space list 2>/dev/null | awk -F' \| ' -v n="$project_name" '$2==n{print $1}' | head -1) [ -z "$space_id" ] && space_id=$(monotask space create "$project_name" 2>&1 | grep -oE '[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}') [ -z "$space_id" ] && { echo "ERROR: Could not find or create space '$project_name'"; exit 1; } board_id=$(monotask board create "release" --json | jq -r '.id // empty') [ -z "$board_id" ] && { echo "ERROR: Failed to create release board"; exit 1; } monotask space boards add "$space_id" "$board_id" >/dev/null 2>&1 || true todo_col=$(monotask column create "$board_id" "Todo" --json | jq -r '.id') doing_col=$(monotask column create "$board_id" "Doing" --json | jq -r '.id') done_col=$(monotask column create "$board_id" "Done" --json | jq -r '.id') - Proceed with complexity assessment below
- At end: follow mastermind-protocol/SKILL.md Brain Write Procedure (namespace:
release)
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 · 182 lines · 38 tokens per session scan A 3eb628ac7fb3
mastermind-release is a skill published in the GitHub repository monoes/monomind (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 38 tokens to every session and 2,010 once invoked, about $0.0002 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
publish-harness
Publish a generated harness to npm — runs the smoke test, signs the witness manifest, and dispatches npm publish --provenance from your tagged release.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
publish-site
Put a finished website online on the Commander's own hosting account (GitHub Pages, Cloudflare Pages or Netlify): preview it, publish a saved version, check the live address really works, and keep a way to roll back.