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/auto-agent)<a href="https://agentmods.dev/commands/monoes/monomind/auto-agent"><img src="https://agentmods.dev/badge/commands/monoes/monomind/auto-agent/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/auto-agent"><img src="https://agentmods.dev/badge/commands/monoes/monomind/auto-agent.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.00012 | $0.00503 |
| Opus 5.5 | $0.00005 | $0.00201 |
| Sonnet 5.5 | $0.00002 | $0.00101 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
automation:auto-agent 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
auto-agent
Automatically spawn agents based on task requirements.
Usage
npx monomind agent spawn [options]
Options
--type, -t <type>- Agent type:coder,tester,researcher,coordinator,architect,analyst--name, -n <name>- Agent name--task <description>- Task description--timeout <ms>- Timeout in milliseconds--auto-tools- Enable automatic tool selection
Examples
Spawn a coder agent for a task
npx monomind agent spawn --type coder --task "Build a REST API with authentication"
Spawn coordinator with auto tools
npx monomind agent spawn --type coordinator --auto-tools --task "Refactor codebase"
Check spawned agent status
npx monomind agent list
npx monomind agent status --id <agent-id>
How It Works
- Task Analysis — Parses task description and identifies required skills
- Agent Selection — Matches skills to agent type (
coder,architect,tester, etc.) - Topology Selection — Chooses swarm structure for multi-agent tasks
- Spawning — Creates agent with role, assigns subtasks, enables coordination
Agent Types
| Type | Best For |
|---|---|
architect |
System design, architecture decisions |
coder |
Implementation, code generation |
tester |
Test creation, quality assurance |
analyst |
Performance, optimization |
researcher |
Documentation, best practices |
coordinator |
Task management, progress tracking |
Integration with Claude Code
// Spawn a single specialized agent
mcp__monomind__agent_spawn({
type: "coder",
name: "API Builder",
task: "Build authentication system",
capabilities: ["typescript", "rest-api"]
})
See Also
agent list— list all active agentsagent status— check agent statusswarm init— initialize a multi-agent swarmworkflow-select— choose predefined workflows
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 · 81 lines · 12 tokens per session scan A 1df4c390040d
automation:auto-agent is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 503 once invoked, about $0.0000 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.