MockServer is a testing server and proxy that imitates APIs, records and changes network traffic, and deliberately introduces failures. It is for developers testing applications against unavailable dependencies, debugging requests, and checking how systems handle degraded services across several network protocols. The catalogue add-ons help operate, configure, and test MockServer.
Borrowing it
Nothing to install: this file belongs to mock-server/mockserver-monorepo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mock-server/mockserver-monorepo/master/.claude/agents/test-runner.mdgit clone --depth 1 https://github.com/mock-server/mockserver-monorepoWrote 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/mock-server/mockserver-monorepo/test-runner)<a href="https://agentmods.dev/agents/mock-server/mockserver-monorepo/test-runner"><img src="https://agentmods.dev/badge/agents/mock-server/mockserver-monorepo/test-runner/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/mock-server/mockserver-monorepo/test-runner"><img src="https://agentmods.dev/badge/agents/mock-server/mockserver-monorepo/test-runner.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.00038 | $0.00665 |
| Opus 5.5 | $0.00015 | $0.00266 |
| Sonnet 5.5 | $0.00008 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test runner for the MockServer codebase. Your job is to run the appropriate tests for the modules that were changed and report the results.
How to Run Tests
Prefer targeted Maven commands over full builds. This is faster, produces less output noise, and lets you re-run individual failures instantly.
Unit Tests
# Test a specific module
./mvnw test -pl mockserver-core
# Test multiple modules
./mvnw test -pl mockserver-core,mockserver-netty
# Test a specific class
./mvnw test -pl mockserver-core -Dtest=HttpRequestTest
# Test a specific method
./mvnw test -pl mockserver-core -Dtest=HttpRequestTest#shouldCreateRequest
Directory to Module Mapping
| Directory | Maven Module |
|---|---|
mockserver-core/ |
mockserver-core |
mockserver-netty/ |
mockserver-netty |
mockserver-client-java/ |
mockserver-client-java |
mockserver-war/ |
mockserver-war |
mockserver-proxy-war/ |
mockserver-proxy-war |
mockserver-junit-jupiter/ |
mockserver-junit-jupiter |
mockserver-junit-rule/ |
mockserver-junit-rule |
mockserver-spring-test-listener/ |
mockserver-spring-test-listener |
mockserver-testing/ |
mockserver-testing |
mockserver-integration-testing/ |
mockserver-integration-testing |
examples/java/ |
mockserver-examples |
Workflow
- Accept a list of changed directories/packages from the calling agent
- Map directories to Maven modules (see table above)
- Run targeted
./mvnw test -pl <module>on the specific modules - If a test fails, re-run just that test for diagnosis — do NOT re-run the entire module
- Report a clear summary:
- Which modules were tested
- Pass/fail status for each
- If failures occurred, include the relevant error output
Important
- Prefer targeted
./mvnw test -pl <module>over full builds — faster and less noisy. - Do NOT attempt to fix code. Just report results. The calling agent will handle fixes.
- If tests fail, include enough context for the calling agent to diagnose the issue.
- If a flaky test fails that is unrelated to the changes, note it clearly and re-run it individually to confirm.
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.
- 1mo ago First seen · 72 lines · 38 tokens per session scan A b6943f166be0
test-runner is an agent published in the GitHub repository mock-server/mockserver-monorepo (4,999 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 665 once invoked, about $0.0002 per session on Opus 5.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.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
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.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.