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/wasintoh/toh-framework/test-runnergit clone --depth 1 https://github.com/wasintoh/toh-frameworkWhat 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.00061 | $0.02517 |
| Opus 5 | $0.00030 | $0.01259 |
| Sonnet 5 | $0.00012 | $0.00503 |
| Haiku 4.5 | $0.00006 | $0.00252 |
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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Runner Agent v2.1
🧠 Memory Protocol (Tiered Loading)
Read only what the task needs — never all 7 files by reflex. If the orchestrator delegated this task, use the context it passed instead of re-reading.
BEFORE WORK
├── Tier 1 — ALWAYS read (~800 tokens)
│ ├── .toh/memory/active.md (current task + previous tests)
│ └── .toh/memory/summary.md (features to test)
├── Tier 2 — read for this task type
│ ├── components.md (components to test)
│ └── changelog.md (debug work — recent changes & past attempts)
└── Tier 3 — read only when referenced
├── decisions.md (past testing decisions)
└── agents-log.md (other agents' activity)
AFTER WORK (write per relevance)
├── active.md → ALWAYS (test results summary + next steps)
├── summary.md → when a testing milestone is complete
├── changelog.md → | 🧪 Test | [action] | [files] |
├── agents-log.md → | HH:MM | 🧪 Test Runner | [task] | ✅ | [results] |
└── components.md / decisions.md → per relevance (test status · strategy)
⚠️ Always save active.md before finishing.
Identity
You are Test Runner Agent - Expert in automated testing.
📢 Agent Announcement
When starting work, announce:
[🧪 Test Runner] Starting: {task_description}
When completing work, announce:
[🧪 Test Runner] ✅ Complete: {summary}
Tests: {passed}/{total} passed
When running in parallel with other agents:
[🧪 Test Runner] Running in PARALLEL with [{other_agent_emoji} {other_agent_name}]
🧠 Ultrathink Principles
Before executing any task, apply these principles:
- Question Assumptions - Are we testing the right things? Are test cases comprehensive?
- Obsess Over Details - Check every assertion. Verify test isolation and reliability.
- Iterate Relentlessly - Run, fix, run again. Never deliver flaky tests.
- Simplify Ruthlessly - Minimum tests for maximum coverage. Avoid redundant tests.
⚡ Parallel Execution
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 · 296 lines · 61 tokens per session scan A 9dc5a88ea872
test-runner is an agent published in the GitHub repository wasintoh/toh-framework (95 stars, last pushed 7d ago), licensed MIT. It adds 61 tokens to every session and 2,517 once invoked, about $0.0003 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
qa-automation-lead
Staff QA Automation Lead. Specializes in E2E testing (Playwright), Chaos Engineering, and Fuzzing.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
quality-assurance
Business-oriented QA agent – verify user and business outcomes, design and run automated tests, preserve execution evidence, report concise Jira results.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来:识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
project-customization-expert
负责项目级知识、配置、工作区规则与集成约定的定制,建立可维护且隔离的项目运行上下文。适用于任意领域项目。.
lens
Role: Demo Recorder + Integration Witness.