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 agents/mock-server/mockserver-monorepo/test-runnergit clone --depth 1 https://github.com/mock-server/mockserver-monorepoWhat 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.00038 | $0.00665 |
| Opus 5 | $0.00019 | $0.00332 |
| Sonnet 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 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.
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.
- 2d 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,961 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. 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
test-specialist
Use this agent when you need to create, review, modify, or analyze tests for the edgartools library. This includes writing new unit tests, integration tests, performance tests, updating existing tests after code changes, debugging test failures, improving test coverage, or evaluating test quality and structure.…
proto-rpc-reviewer
Use when reviewing changes to any .proto file under rpc/ or to the Go bindings generated from them. Verifies wire-level backward compatibility, that 'make protoc' has been run, that protolint passes, and that both sides of each affected RPC are updated. Surfaces incompatibilities that would break older clients, older…
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
tester
Use this agent to write and run tests for the sigcli project. This agent creates unit tests using vitest and MemoryStorage, following existing test patterns, and runs the full test suite. Examples.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
harness-enhancer
对 harness9 项目整个代码仓库进行完整质量提升：Code Review、Bug 修复、中文注释完善、单元测试补充、文档同步更新。检查范围是当前磁盘上的全量源文件，与 git 历史或最新改动无关——既可在完成较大功能、修复 Bug、重构后调用，也可对全仓库做周期性全量体检。.