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 agentmods add agents/airmcp-com/mcp-standards/agent-spawninggit clone --depth 1 https://github.com/airmcp-com/mcp-standardsWrote 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/agents/airmcp-com/mcp-standards/agent-spawning)<a href="https://agentmods.dev/agents/airmcp-com/mcp-standards/agent-spawning"><img src="https://agentmods.dev/badge/agents/airmcp-com/mcp-standards/agent-spawning.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00175 |
| Opus 5 | $0.00000 | $0.00088 |
| Sonnet 5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
agent-spawning 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 3d 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.
This is a copy
100% identical to agent-spawning — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
agent-spawning
Guide to spawning agents with Claude Code's Task tool.
Using Claude Code's Task Tool
CRITICAL: Always use Claude Code's Task tool for actual agent execution:
// Spawn ALL agents in ONE message
Task("Researcher", "Analyze requirements...", "researcher")
Task("Coder", "Implement features...", "coder")
Task("Tester", "Create tests...", "tester")
MCP Coordination Setup (Optional)
MCP tools are ONLY for coordination:
mcp__claude-flow__swarm_init { topology: "mesh" }
mcp__claude-flow__agent_spawn { type: "researcher" }
Best Practices
- Always spawn agents concurrently
- Use Task tool for execution
- MCP only for coordination
- Batch all operations
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.
- 3d ago First seen · 29 lines · 0 tokens per session scan A 74bfe922137a
agent-spawning is an agent published in the GitHub repository airmcp-com/mcp-standards (3 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 175 tokens. A static security scan graded it A with 0 findings. It is 100% identical to agent-spawning, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
ci-architect
CI/CD pipeline architect specializing in workflow configuration, job orchestration, and pipeline optimization. Use PROACTIVELY when the user asks to "set up CI", "configure GitHub Actions", "create pipeline", "fix CI workflow", or needs help designing compliant CI/CD pipelines.
quality-enforcer
Code quality specialist enforcing formatting, linting, error handling, and documentation standards. Use PROACTIVELY when the user asks to "check code quality", "review formatting", "enforce lint rules", "fix code style", or needs code quality assessment and remediation.
compliance-auditor
Comprehensive SDLC compliance auditor that reviews projects against all standards. Use PROACTIVELY when the user asks to "audit compliance", "check SDLC requirements", "review project standards", "validate compliance", or wants a full assessment of how well a project meets SDLC requirements.
security-reviewer
Security-focused reviewer specializing in vulnerability assessment, supply chain security, and secure coding practices. Use PROACTIVELY when the user asks to "review security", "audit dependencies", "check for vulnerabilities", "security scan", or needs security-specific compliance assessment.
researcher
Explores the codebase and returns concise summaries of code structure, relationships, and patterns. Use for understanding existing code before making changes.
test-runner
Runs backend and frontend tests, analyzes output, and returns only failures and relevant diagnostics. Use after writing or modifying code.