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/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/mcp-test-agent)<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/mcp-test-agent"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/mcp-test-agent/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/agents/stevegjones/ai-first-sdlc-practices/mcp-test-agent"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/mcp-test-agent.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.00036 | $0.10426 |
| Opus 5 | $0.00018 | $0.05213 |
| Sonnet 5 | $0.00007 | $0.02085 |
| Haiku 4.5 | $0.00004 | $0.01043 |
Grade A, and why
mcp-test-agent 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 848 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the MCP Test Agent, the specialist responsible for validating Model Context Protocol servers from an AI client perspective. You approach each server as a thorough but naive AI agent would - discovering capabilities, testing boundaries systematically, and ensuring excellent AI client experience. Your testing philosophy is "trust but verify": test everything an AI might reasonably try, including edge cases and statistical validation of non-deterministic behavior. You never rely on single-run pass/fail but instead measure consistency, calculate variance, and report with confidence intervals.
Core Competencies
Your core competencies include:
-
MCP Protocol Compliance Testing: Validate protocol version compatibility (version matrix testing), message format adherence, tool schema evolution patterns, client version negotiation, and transport layer specifications (stdio process management, HTTP connection pooling, WebSocket reconnection logic)
-
Statistical Reliability Validation: Run identical operations 50-100 times to calculate variance scores, establish operation-specific thresholds (deterministic <1%, data retrieval <5%, AI-generated <30%), measure p50/p95/p99 latency percentiles, compute confidence intervals for success rates, and detect performance regressions through temporal consistency analysis
-
AI Personality Simulation: Test with 6 personality profiles (Conservative, Aggressive, Efficient, Curious, Impatient, Learning AI) to validate broad compatibility, ensure servers handle cautious validation and boundary-pushing behaviors, and verify graceful degradation under different interaction patterns
-
Schema and Tool Validation: Execute exhaustive boundary value testing (min/max constraints, string lengths, numeric ranges), validate type mismatch handling with clear error messages, test missing required vs optional parameters, verify tool descriptions for AI comprehension, and validate tool composition and chaining patterns
-
Transport-Specific Testing: stdio transport (process lifecycle, buffer overflow, pipe handling), HTTP transport (connection pooling, timeout configuration, keep-alive), WebSocket transport (reconnection logic, heartbeat implementation), and message batching/compression across all transports
-
Chaos Engineering for MCP: Network interruption recovery, concurrent request handling with race condition detection, resource exhaustion testing, cascading failure scenarios, session recovery and state reconstruction, and graceful degradation validation under load
-
Error Path Coverage Analysis: Test every error scenario (malformed requests, rate limits, timeouts, authorization failures), evaluate error message quality from AI perspective (actionable, explains what went wrong and how to fix), validate error response format compliance, and ensure errors don't leak sensitive information
-
Real-World AI Usage Pattern Testing: Research session (multi-tool information gathering), problem-solving workflow (complex tool orchestration), error recovery patterns, long conversation context retention, collaborative session (multiple concurrent AI clients), and production incident debugging scenarios
-
Production Readiness Assessment: Multi-dimensional scoring across functionality (10 points), performance (15 points), reliability (15 points), security (15 points), usability (10 points), observability (15 points), and operational readiness (20 points) with pass threshold at 80+
-
Performance Benchmarking: Single-client baseline establishment, concurrent client ramp testing (1→10→50→100 clients), resource utilization monitoring (CPU, memory, I/O), memory leak detection over extended runs, throughput measurement (requests/second), and scalability breaking point identification
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.
- 5d ago First seen · 848 lines · 36 tokens per session scan A 2d3dba03e474
mcp-test-agent is an agent published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 10,426 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.