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/actionhero/keryx/test-runnergit clone --depth 1 https://github.com/actionhero/keryxWhat 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.00000 | $0.00442 |
| Opus 5 | $0.00000 | $0.00221 |
| Sonnet 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 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.
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.
- 2d ago First seen · 51 lines · 0 tokens per session scan A 898177759632
test-runner is an agent published in the GitHub repository actionhero/keryx (33 stars, last pushed 10d 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
switchboard
This project uses the Switchboard protocol for cross-IDE agent collaboration.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
docs-impact
Reviews documentation affected by code changes. Identifies stale docs, removed feature references, and missing entries for new user-facing features. Reports findings with specific fixes. Advisory only - does not modify files.
Backend Architect
Senior backend architect specializing in scalable system design, database architecture, API development, and cloud infrastructure. Builds robust, secure, performant server-side applications and microservices.
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.