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.
git 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/commands/monoes/monomind/release)<a href="https://agentmods.dev/commands/monoes/monomind/release"><img src="https://agentmods.dev/badge/commands/monoes/monomind/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/commands/monoes/monomind/release"><img src="https://agentmods.dev/badge/commands/monoes/monomind/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.00018 | $0.00327 |
| Opus 5.5 | $0.00007 | $0.00131 |
| Sonnet 5.5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
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 yesterday.
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.
What it actually says
First — extract repeat flags: Follow the REPEAT PREAMBLE from mastermind-repeat/SKILL.md. Extracts --repeat, --tillend, --maxruns, --wait, --rep, --loop from $ARGUMENTS before all other parsing. If is_continuation = true, skip the empty-prompt check and intake below.
Parse $ARGUMENTS for:
--autoflag → mode = auto--confirmflag → mode = confirm--project <name>→ project_name =- Remaining text = prompt
If prompt is empty: ask "What would you like to release or deploy?"
Load brain context for the release domain (follow mastermind-protocol/SKILL.md Brain Load Procedure).
Run intake if prompt is vague (follow mastermind-intake/SKILL.md — stop at Q3, domain is already known as release).
Default mode for this command: auto (unless --confirm flag present or intake Q4 says confirm).
Invoke Skill("mastermind-release") passing: brain_context, prompt, project_name, board_id (create if needed), mode.
After skill returns: follow mastermind-protocol/SKILL.md Brain Write Procedure for domain release.
Invoke Skill("mastermind-repeat") now to execute the REPEAT POSTAMBLE. This is a required tool call — do not skip it.
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.
- yesterday First seen · 26 lines · 18 tokens per session scan A 0ddd59f18986
release is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 327 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 commands, from other repositories
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
ci
Trigger GitHub Actions CI/CD builds, sign, publish, or check CI status.
work-flow-release
Complete workflow to prepare and publish a release.
guardar
Grupo: Rutina del día a día En una frase: Guardar cambios — bump, commit y push al remoto de este repo. El DT oficial solo con /oficial activo. Cuándo: Al cerrar bloque con cambios. El dígito lo elige la IA; si nombrás patch, minor o major, usa ese. Quién: Cualquier operador del repo.