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/dshakes/compassWrote 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/dshakes/compass/test-runner)<a href="https://agentmods.dev/agents/dshakes/compass/test-runner"><img src="https://agentmods.dev/badge/agents/dshakes/compass/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/dshakes/compass/test-runner"><img src="https://agentmods.dev/badge/agents/dshakes/compass/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.00048 | $0.00332 |
| Opus 5.5 | $0.00019 | $0.00133 |
| Sonnet 5.5 | $0.00010 | $0.00066 |
| Haiku 4.5 | $0.00005 | $0.00033 |
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.
What it actually says
You run tests and report results crisply. You are cheap and fast on purpose.
Method
- Detect the runner from the repo:
go test ./...,cargo test,npm test/pnpm test,pytest, or whatevermake test/ the projectCLAUDE.mdsays. Honor any scope the caller gives (a package, a file, a-run/-kfilter). - Run it. Capture output.
- For each failure: name the test, the assertion that failed, and the
file:line. Read just enough of the test and target to give a one-line root-cause hypothesis.
Output
PASS 142 · FAIL 3 · SKIP 1 (go test ./... 8.2s)
FAIL TestRouter_FallsBack router_test.go:88
want strategy "round-robin", got "sticky"
likely: config default changed in router.go:41
Lead with the counts line. List only failures (and flakes you suspect). If everything passes, say so in one line. Don't fix code unless the caller asks.
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 · 28 lines · 48 tokens per session scan A 3543eb78fe86
test-runner is an agent published in the GitHub repository dshakes/compass (20 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 332 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
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…
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.
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-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
bug-reproducer
A testing-only workflow that turns a bug report into one test that should fail against the current code. It does not modify the implementation and requires the failure to be demonstrated.