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/specialagents)<a href="https://agentmods.dev/commands/monoes/monomind/specialagents"><img src="https://agentmods.dev/badge/commands/monoes/monomind/specialagents/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/specialagents"><img src="https://agentmods.dev/badge/commands/monoes/monomind/specialagents.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.00021 | $0.00896 |
| Opus 5.5 | $0.00008 | $0.00358 |
| Sonnet 5.5 | $0.00004 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
specialagents 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activate a specialist agent persona. Three modes:
Direct: /mastermind:specialagents <slug> — skip selection, activate immediately.
Interactive: /mastermind:specialagents — guided category → agent selection.
Auto: /mastermind:specialagents auto — LLM picks the best match from conversation context.
Step 0 — Detect mode
- If
$ARGUMENTSis a non-empty string that is notauto:- Treat it as a slug/name → jump to Step 4: Activate.
- If
$ARGUMENTSisautoor the user's message contains words like "auto", "automatically", "pick for me", "best agent", "suggest an agent":- Jump to Auto flow.
- Otherwise → Interactive flow.
Interactive flow
Step 1 — List categories
Run:
node "${CLAUDE_PROJECT_DIR:-$(pwd)}/.claude/helpers/hook-handler.cjs" list-extras 2>/dev/null
Parse the output. Extract the category names (lines like === ACADEMIC === → academic). Display them as a numbered list:
Available agent categories:
1. academic
2. design
3. marketing
4. paid-media
5. product
6. project-management
7. sales
8. specialized
9. support
Enter a number or category name:
Wait for the user to reply with their choice.
Step 2 — List agents in chosen category
Map the user's reply to the lowercase category slug (e.g. "1" → academic, "Project Management" → project-management).
Run:
node "${CLAUDE_PROJECT_DIR:-$(pwd)}/.claude/helpers/hook-handler.cjs" list-extras <category> 2>/dev/null
Parse the agents listed. Display them numbered:
Agents in <category>:
1. slug-name — Short description
2. ...
Enter a number or agent slug:
Wait for the user to reply.
Step 3 — Confirm selection
Echo back: Activating agent: <slug>
Jump to Step 4: Activate.
Auto flow
Auto Step 1 — Fetch all categories
Run:
node "${CLAUDE_PROJECT_DIR:-$(pwd)}/.claude/helpers/hook-handler.cjs" list-extras 2>/dev/null
Read the full output. Based on the current conversation context (the user's request, task description, or recent messages), decide which category is the best fit. Do not ask the user — choose silently.
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 · 125 lines · 21 tokens per session scan A a5ad4c6f92d4
specialagents is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 896 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
doctor
Health-check the harness: kernel load, MCP wiring, memory backend, host adapter.
review-diff
Review the current working diff for correctness, security, and reuse.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
prp-plan
Create comprehensive feature implementation plan with codebase analysis and pattern extraction.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
checklist
Generate a custom checklist for the current feature based on user requirements.