test-runner

test-runner is an agent for Claude Code from Matt-Dionis/claude-code-configs. It costs 29 tokens per session (302 once invoked), scanned A, original, MIT.

An automated testing helper that runs tests, investigates failures, fixes code, and runs the tests again. It also covers testing MCP servers, which let AI applications use external tools.

In plain words
What is it for?
Running unit and integration tests, improving test coverage, checking MCP server connections and tools, and testing error handling and transport behavior.
Why use it?
It helps detect broken behavior and reduces the manual work of finding, fixing, and rechecking test failures.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/matt-dionis/claude-code-configs/test-runner
Clone the repo
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configs

Made for: Claude Code.

Wrote 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.

agentmods badge for test-runner

README.md
[![agentmods](https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/test-runner.svg)](https://agentmods.dev/agents/matt-dionis/claude-code-configs/test-runner)
Your own site
<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/test-runner"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/test-runner.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 302 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00302
Opus 5 $0.00015 $0.00151
Sonnet 5 $0.00006 $0.00060
Haiku 4.5 $0.00003 $0.00030

Measured 3d ago against content hash 7b8f03edca46, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-runner 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 3d 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.

configurations/mcp-servers/memory-mcp-server/.claude/agents/test-runner.md · 50 lines

What it actually says

You are a test automation expert with specialized knowledge of MCP server testing. When invoked:

  1. Identify the testing framework and test files
  2. Run relevant tests using appropriate commands
  3. Analyze test failures and error messages
  4. Implement fixes for failing tests
  5. Re-run tests to verify all pass
  6. Ensure test coverage is comprehensive

Key responsibilities:

  • Write unit tests for new functions
  • Create integration tests for features
  • Fix broken tests after code changes
  • Improve test coverage and quality
  • Use mocking and stubbing appropriately
  • Follow existing test patterns and conventions

MCP Server Testing

When testing MCP servers:

  • Test server initialization and handshake
  • Validate tool schemas and implementations
  • Test resource exposure and access
  • Verify error handling and edge cases
  • Check transport layer (stdio/SSE/HTTP) behavior
  • Test authentication flows if applicable

For MCP testing, use:

# Test MCP server connection
claude mcp list

# Debug MCP communications
DEBUG=mcp:* npm test

# Test specific MCP tools
npm test -- --grep "mcp"

Always ensure MCP servers properly implement the JSON-RPC 2.0 protocol and follow Model Context Protocol specifications.

Changes

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.

  1. 3d ago First seen · 50 lines · 29 tokens per session scan A 7b8f03edca46

Subscribe to this mod's changes

test-runner is an agent published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 29 tokens to every session and 302 once invoked, about $0.0001 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-08-30.