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 commands/airmcp-com/mcp-standards/analysisgit 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/analysis)<a href="https://agentmods.dev/commands/airmcp-com/mcp-standards/analysis"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/analysis.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.1 | $0.00000 | $0.00529 |
| Opus 5 | $0.00000 | $0.00264 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
analysis 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 2d 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 analysis — 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
Analysis Swarm Strategy
Purpose
Comprehensive analysis through distributed agent coordination.
Activation
Using MCP Tools
// Initialize analysis swarm
mcp__claude-flow__swarm_init({
"topology": "mesh",
"maxAgents": 6,
"strategy": "adaptive"
})
// Orchestrate analysis task
mcp__claude-flow__task_orchestrate({
"task": "analyze system performance",
"strategy": "parallel",
"priority": "medium"
})
Using CLI (Fallback)
npx claude-flow swarm "analyze system performance" --strategy analysis
Agent Roles
Agent Spawning with MCP
// Spawn analysis agents
mcp__claude-flow__agent_spawn({
"type": "analyst",
"name": "Data Collector",
"capabilities": ["metrics", "logging", "monitoring"]
})
mcp__claude-flow__agent_spawn({
"type": "analyst",
"name": "Pattern Analyzer",
"capabilities": ["pattern-recognition", "anomaly-detection"]
})
mcp__claude-flow__agent_spawn({
"type": "documenter",
"name": "Report Generator",
"capabilities": ["reporting", "visualization"]
})
mcp__claude-flow__agent_spawn({
"type": "coordinator",
"name": "Insight Synthesizer",
"capabilities": ["synthesis", "correlation"]
})
Coordination Modes
- Mesh: For exploratory analysis
- Pipeline: For sequential processing
- Hierarchical: For complex systems
Analysis Operations
// Run performance analysis
mcp__claude-flow__performance_report({
"format": "detailed",
"timeframe": "24h"
})
// Identify bottlenecks
mcp__claude-flow__bottleneck_analyze({
"component": "api",
"metrics": ["response-time", "throughput"]
})
// Pattern recognition
mcp__claude-flow__pattern_recognize({
"data": performanceData,
"patterns": ["anomaly", "trend", "cycle"]
})
Status Monitoring
// Monitor analysis progress
mcp__claude-flow__task_status({
"taskId": "analysis-task-001"
})
// Get analysis results
mcp__claude-flow__task_results({
"taskId": "analysis-task-001"
})
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.
- 2d ago First seen · 96 lines · 0 tokens per session scan A 13916bbe3f03
analysis is a command 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 529 tokens. A static security scan graded it A with 0 findings. It is 100% identical to analysis, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
spec
Spec-first design: a gap-closing interview that produces a complete spec, with a quality controller that blocks until every section is answered and every question resolved.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.