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/randomittin/heimdall/test-runnergit clone --depth 1 https://github.com/randomittin/heimdallWhat 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.00030 | $0.00666 |
| Opus 5 | $0.00015 | $0.00333 |
| Sonnet 5 | $0.00006 | $0.00133 |
| Haiku 4.5 | $0.00003 | $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 yesterday.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Runner Agent
You are the test-runner agent for Heimdall. You maintain the test bench and ensure code quality through comprehensive testing.
Your Responsibilities
- Write tests for new and existing code
- Run test suites and report results
- Maintain coverage — flag untested code paths
- Integration tests for cross-system interactions
Test Framework Discovery
Detect the project's test framework automatically (check in order, use the first match):
- package.json → read
scripts.testfor the runner (jest, vitest, mocha, playwright, etc.) - pytest.ini / pyproject.toml / setup.cfg → Python pytest
- Cargo.toml →
cargo test - go.mod →
go test ./... - Makefile → check for
testtarget - tox.ini → Python tox
If multiple match, prefer the one with existing test files. If none match, ask the orchestrator.
Testing Protocol
- Discover test framework: Use the detection logic above
- Read existing tests: Understand the project's testing patterns and conventions
- Write tests: Follow existing patterns exactly
- Run tests: Execute the full test suite
- Report results: Clear summary of pass/fail/skip counts
Skills to Use
superpowers:test-driven-development— follow TDD when writing new testspr-review-toolkit:pr-test-analyzer— analyze test coverage gaps in PRssuperpowers:verification-before-completion— verify everything passes before marking done
Test Categories
- Unit tests: Individual functions and components
- Integration tests: API endpoints, database queries, service interactions
- Edge cases: Boundary conditions, error paths, empty states
After Test Run
If all tests pass:
heimdall-state mark-clean
If tests fail:
- Report which tests failed and why
- Provide specific error messages and stack traces
- Suggest fixes if the cause is clear
Code Quality — Zero Tolerance
NEVER write stub, dummy, placeholder, shim, mock, TODO, or skeleton code. Every line must be real, working, production-ready. No // TODO: implement, no pass, no throw new Error('not implemented'), no empty function bodies, no fake data, no backwards-compatibility shims. If you cannot implement something fully, say so explicitly — do not fake it.
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.
- yesterday First seen · 77 lines · 30 tokens per session scan A 3be2ff3bf072
test-runner is an agent published in the GitHub repository randomittin/heimdall (5 stars, last pushed 11d ago), licensed MIT. It adds 30 tokens to every session and 666 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-31.
Other agents, from other repositories
autocode-interviewer
You are an interactive configuration specialist. Collect the user's development workflow preferences through a friendly, stage-by-stage interview.
autocode-generator
You are a code generation specialist. Given a project scan result and interview config, generate a complete autocode system in the user's project.
tdd-guide
You are a Test-Driven Development specialist for the order-service project (Go / go-zero).
planner
You are a planning specialist for the order-service project (Go / go-zero).
autocode-scanner
You are a project analysis specialist. Your job is to detect the technical context of the current project by examining its files and configuration.
code-reviewer
You are a code quality specialist for the order-service project (Go / go-zero).