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/ops)<a href="https://agentmods.dev/commands/monoes/monomind/ops"><img src="https://agentmods.dev/badge/commands/monoes/monomind/ops/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/ops"><img src="https://agentmods.dev/badge/commands/monoes/monomind/ops.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.00575 |
| Opus 5.5 | $0.00007 | $0.00230 |
| Sonnet 5.5 | $0.00004 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
ops 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 operations task would you like to automate or optimize?"
Load brain context for the ops 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 ops).
Default mode for this command: auto (unless --confirm flag present or intake Q4 says confirm).
Pick the specialist (there is no mastermind-ops skill package — the work is done by a picked agent). In order, per mastermind-agent-select/SKILL.md:
- The prompt's
[PICK]line, if it fits this ops task. mcp__monomind__pick({ task: prompt, kind: "both", categories: ["specialized", "engineering", "core"], top: 3 })— useagents.ranked[0].name; ifskills.ranked[0]clearly fits, load it with itsinvoke.- No MCP: the Standard Selection Block from
mastermind-agent-select/SKILL.mdwithCATEGORIES="specialized engineering core",TOP_N=3. - Nothing returned:
Workflow Optimizer.
Spawn the picked agent via the Task tool, passing: brain_context, prompt, project_name, board_id (create if needed), mode — as a briefing that follows the Monotask Task Briefing Standard in mastermind-protocol/SKILL.md and includes the AGENT DELEGATION CAPABILITY block from mastermind-delegation/SKILL.md. In confirm mode, show the agent's plan or draft to the user before anything is published or sent.
After the agent returns: follow mastermind-protocol/SKILL.md Brain Write Procedure for domain ops.
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 · 32 lines · 18 tokens per session scan A 62c6b8fbce35
ops 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 575 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
multi-repo-swarm
Coordinate AI swarms across multiple repositories, enabling organization-wide automation and intelligent cross-project collaboration.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
auto-agent
Automatically spawn and manage agents based on task requirements.
jira
Retrieve a Jira ticket, analyze requirements, update status, or add comments. Uses the jira-integration skill and MCP or REST API.
bienvenida
Grupo: Rutina del día a día En una frase: Primera vez post-clone — checklist + mensaje de bienvenida con commands recomendados (incluye /setup si falta estructura). Cuándo: Justo después de clonar o abrir el DT por primera vez; la IA también puede mostrarlo sin invocación si no hay sesión local. Quién: Cualquier…
morning
The coffee report — cross-project map deltas, arrives on its own (scheduled).