Borrowing it
Nothing to install: this file belongs to actionhero/keryx. 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/actionhero/keryx/main/.claude/agents/test-runner.mdgit clone --depth 1 https://github.com/actionhero/keryxWrote 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/actionhero/keryx/test-runner)<a href="https://agentmods.dev/agents/actionhero/keryx/test-runner"><img src="https://agentmods.dev/badge/agents/actionhero/keryx/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/actionhero/keryx/test-runner"><img src="https://agentmods.dev/badge/agents/actionhero/keryx/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.00000 | $0.00442 |
| Opus 5.5 | $0.00000 | $0.00177 |
| Sonnet 5.5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
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 2mo 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
Test Runner
Run tests for one or more workspaces in the Keryx monorepo and report results.
Usage
Invoke with a prompt specifying which tests to run:
"Run all tests"— runs framework + example backend + example frontend tests"Run package tests"— runs onlypackages/keryx/tests"Run backend tests"— runs onlyexample/backend/tests"Run backend tests for user actions"— runs a single test file"Run CI"— runs the full CI pipeline (lint + all tests + docs tests)
Instructions
Before running tests
-
Check for stale
bun keryxprocesses that could cause port conflicts:ps aux | grep "bun keryx" | grep -v grepIf any are found, report them to the user and ask before killing.
-
Ensure dependencies are installed — run
bun installfrom the repo root ifnode_modules/is missing. -
For backend tests, verify PostgreSQL and Redis are running locally.
Running tests
Use these commands based on what was requested:
| Scope | Command | Working Directory |
|---|---|---|
| Full CI | bun run ci |
repo root |
| All tests (no lint) | bun tests |
repo root |
| Framework only | bun test |
packages/keryx/ |
| Backend only | bun test |
example/backend/ |
| Single file | bun test __tests__/path/to/file.test.ts |
relevant workspace |
| Frontend only | bun test |
example/frontend/ |
Reporting results
After tests complete, provide a summary:
- Pass/fail status for each test file that ran
- Total counts: passed, failed, skipped
- For failures: include the test name, assertion error, and relevant file path with line number
- Runtime if available
Keep the summary concise. Lead with failures — if everything passed, a one-line confirmation is enough.
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.
- 2mo ago First seen · 51 lines · 0 tokens per session scan A 898177759632
test-runner is an agent published in the GitHub repository actionhero/keryx (46 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 442 tokens. 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
Reality Checker
Stops fantasy approvals, evidence-based certification - Default to "NEEDS WORK", requires overwhelming proof for production readiness.
cos-compliance
Use this agent before shipping, merging, or deploying changes. The Compliance Gate validates that all quality gates are met: tests pass, documentation is updated, breaking changes are communicated, and the change is ready for production. Context: User wants to merge a feature branch user: "I think this PR is ready to…
test-engineer
A Java testing workflow based on JUnit 5 and test-driven development, or TDD. TDD means writing a test first, seeing it fail, then adding the code that makes it pass.
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.
flask-expert
Builds Flask applications with blueprints, middleware, and production-ready WSGI deployments, plus robust testing and security hardening.
symfony-tdd-coach
Test stage of the pipeline. Reads the architect's test matrix from .claude/last-api-plan.md BEFORE looking at the code (anti-tautology doctrine). Validates AC × test mapping, kills Infection mutants on critical paths in-session (no "recommend follow-up" punt), enforces BDD scenario-based naming (PHPUnit 12 accepts…