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/researchgit 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/research)<a href="https://agentmods.dev/commands/airmcp-com/mcp-standards/research"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/research.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.00790 |
| Opus 5 | $0.00000 | $0.00395 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
research 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 research — 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Swarm Strategy
Purpose
Deep research through parallel information gathering.
Activation
Using MCP Tools
// Initialize research swarm
mcp__claude-flow__swarm_init({
"topology": "mesh",
"maxAgents": 6,
"strategy": "adaptive"
})
// Orchestrate research task
mcp__claude-flow__task_orchestrate({
"task": "research topic X",
"strategy": "parallel",
"priority": "medium"
})
Using CLI (Fallback)
npx claude-flow swarm "research topic X" --strategy research
Agent Roles
Agent Spawning with MCP
// Spawn research agents
mcp__claude-flow__agent_spawn({
"type": "researcher",
"name": "Web Researcher",
"capabilities": ["web-search", "content-extraction", "source-validation"]
})
mcp__claude-flow__agent_spawn({
"type": "researcher",
"name": "Academic Researcher",
"capabilities": ["paper-analysis", "citation-tracking", "literature-review"]
})
mcp__claude-flow__agent_spawn({
"type": "analyst",
"name": "Data Analyst",
"capabilities": ["data-processing", "statistical-analysis", "visualization"]
})
mcp__claude-flow__agent_spawn({
"type": "documenter",
"name": "Report Writer",
"capabilities": ["synthesis", "technical-writing", "formatting"]
})
Research Methods
Information Gathering
// Parallel information collection
mcp__claude-flow__parallel_execute({
"tasks": [
{ "id": "web-search", "command": "search recent publications" },
{ "id": "academic-search", "command": "search academic databases" },
{ "id": "data-collection", "command": "gather relevant datasets" }
]
})
// Store research findings
mcp__claude-flow__memory_usage({
"action": "store",
"key": "research-findings-" + Date.now(),
"value": JSON.stringify(findings),
"namespace": "research",
"ttl": 604800 // 7 days
})
Analysis and Validation
// Pattern recognition in findings
mcp__claude-flow__pattern_recognize({
"data": researchData,
"patterns": ["trend", "correlation", "outlier"]
})
// Cognitive analysis
mcp__claude-flow__cognitive_analyze({
"behavior": "research-synthesis"
})
// Cross-reference validation
mcp__claude-flow__quality_assess({
"target": "research-sources",
"criteria": ["credibility", "relevance", "recency"]
})
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 · 137 lines · 0 tokens per session scan A fa1b2adcca5d
research 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 790 tokens. A static security scan graded it A with 0 findings. It is 100% identical to research, 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.
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
index
The code index: build it, then find, search, refs, outline, and impact instead of grepping blind.
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.