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/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/commands/airmcp-com/mcp-standards/development)<a href="https://agentmods.dev/commands/airmcp-com/mcp-standards/development"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/development/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/airmcp-com/mcp-standards/development"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/development.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.00000 | $0.00531 |
| Opus 5.5 | $0.00000 | $0.00212 |
| Sonnet 5.5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
development 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 1mo 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 development — 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
Development Swarm Strategy
Purpose
Coordinated development through specialized agent teams.
Activation
Using MCP Tools
// Initialize development swarm
mcp__claude-flow__swarm_init({
"topology": "hierarchical",
"maxAgents": 8,
"strategy": "balanced"
})
// Orchestrate development task
mcp__claude-flow__task_orchestrate({
"task": "build feature X",
"strategy": "parallel",
"priority": "high"
})
Using CLI (Fallback)
npx claude-flow swarm "build feature X" --strategy development
Agent Roles
Agent Spawning with MCP
// Spawn development agents
mcp__claude-flow__agent_spawn({
"type": "architect",
"name": "System Designer",
"capabilities": ["system-design", "api-design"]
})
mcp__claude-flow__agent_spawn({
"type": "coder",
"name": "Frontend Developer",
"capabilities": ["react", "typescript", "ui"]
})
mcp__claude-flow__agent_spawn({
"type": "coder",
"name": "Backend Developer",
"capabilities": ["nodejs", "api", "database"]
})
mcp__claude-flow__agent_spawn({
"type": "specialist",
"name": "Database Expert",
"capabilities": ["sql", "nosql", "optimization"]
})
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "Integration Tester",
"capabilities": ["integration", "e2e", "api-testing"]
})
Best Practices
- Use hierarchical mode for large projects
- Enable parallel execution
- Implement continuous testing
- Monitor swarm health regularly
Status Monitoring
// Check swarm status
mcp__claude-flow__swarm_status({
"swarmId": "development-swarm"
})
// Monitor agent performance
mcp__claude-flow__agent_metrics({
"agentId": "architect-001"
})
// Real-time monitoring
mcp__claude-flow__swarm_monitor({
"swarmId": "development-swarm",
"interval": 5000
})
Error Handling
// Enable fault tolerance
mcp__claude-flow__daa_fault_tolerance({
"agentId": "all",
"strategy": "auto-recovery"
})
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.
- 1mo ago First seen · 97 lines · 0 tokens per session scan A 5e723f5e4497
development is a command published in the GitHub repository airmcp-com/mcp-standards (3 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 531 tokens. A static security scan graded it A with 0 findings. It is 100% identical to development, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
init-docs
Fetch official Anthropic Claude Code docs and store as local baseline snapshot.
init
Install the formatters this repository needs, with every command visible before it runs.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.