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/testinggit 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/testing)<a href="https://agentmods.dev/commands/airmcp-com/mcp-standards/testing"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/testing.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.00766 |
| Opus 5 | $0.00000 | $0.00383 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
testing 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.
This is a copy
100% identical to testing — 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Swarm Strategy
Purpose
Comprehensive testing through distributed execution.
Activation
Using MCP Tools
// Initialize testing swarm
mcp__claude-flow__swarm_init({
"topology": "star",
"maxAgents": 7,
"strategy": "parallel"
})
// Orchestrate testing task
mcp__claude-flow__task_orchestrate({
"task": "test application",
"strategy": "parallel",
"priority": "high"
})
Using CLI (Fallback)
npx claude-flow swarm "test application" --strategy testing
Agent Roles
Agent Spawning with MCP
// Spawn testing agents
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "Unit Tester",
"capabilities": ["unit-testing", "mocking", "coverage"]
})
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "Integration Tester",
"capabilities": ["integration", "api-testing", "contract-testing"]
})
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "E2E Tester",
"capabilities": ["e2e", "ui-testing", "user-flows"]
})
mcp__claude-flow__agent_spawn({
"type": "tester",
"name": "Performance Tester",
"capabilities": ["load-testing", "stress-testing", "benchmarking"]
})
mcp__claude-flow__agent_spawn({
"type": "monitor",
"name": "Security Tester",
"capabilities": ["security-testing", "penetration-testing", "vulnerability-scanning"]
})
Test Coverage
Coverage Analysis
// Quality assessment
mcp__claude-flow__quality_assess({
"target": "test-coverage",
"criteria": ["line-coverage", "branch-coverage", "function-coverage"]
})
// Edge case detection
mcp__claude-flow__pattern_recognize({
"data": testScenarios,
"patterns": ["edge-case", "boundary-condition", "error-path"]
})
Test Execution
// Parallel test execution
mcp__claude-flow__parallel_execute({
"tasks": [
{ "id": "unit-tests", "command": "npm run test:unit" },
{ "id": "integration-tests", "command": "npm run test:integration" },
{ "id": "e2e-tests", "command": "npm run test:e2e" }
]
})
// Batch processing for test suites
mcp__claude-flow__batch_process({
"items": testSuites,
"operation": "execute-test-suite"
})
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 · 132 lines · 0 tokens per session scan A 2a61aa79ec78
testing 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 766 tokens. A static security scan graded it A with 0 findings. It is 100% identical to testing, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
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.
audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
test-suite
Run comprehensive test suite with coverage analysis.
test-bar
Generate a floating QA test overlay for the current branch's UI changes. Use when user says /test-bar, needs visual QA scenarios, or wants to test conditional rendering paths.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.
validate
Run SDLC compliance check against the current project. Validates build system, code quality, testing, CI/CD, security, documentation, VCS, and release configurations.