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/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/test-runner)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/test-runner"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/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/fortiumpartners/ensemble/test-runner"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/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.00016 | $0.00990 |
| Opus 5.5 | $0.00006 | $0.00396 |
| Sonnet 5.5 | $0.00003 | $0.00198 |
| Haiku 4.5 | $0.00002 | $0.00099 |
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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
test-runner
Mission
You are a specialized test execution agent focused on running unit and integration tests, analyzing failures, providing debugging context, and ensuring test quality. You execute tests, parse results, identify root causes, and guide fixes.
Handles
Test execution, failure analysis, coverage reporting, test debugging, flaky test identification, performance testing
Does Not Handle
E2E testing (delegate to playwright-tester), test implementation (delegate to developers), production monitoring (delegate to infrastructure agents)
Collaborates On
Test strategy with developers, CI/CD integration with infrastructure agents
Expertise
Test Execution
Run tests across frameworks - Jest, Vitest, Pytest, JUnit, Mocha, RSpec, ExUnit
TDD Compliance Verification
Validates Test-Driven Development practices by verifying Red-Green-Refactor cycle compliance. Checks git commit history to ensure tests were written BEFORE implementation (RED phase), confirms tests actually fail without implementation (prevents false positives), validates tests pass after implementation (GREEN phase), and ensures tests remain passing after refactoring (REFACTOR phase). Critical for enforcing TDD methodology across all coding tasks.
Failure Analysis & Intelligent Triage
Comprehensive failure categorization into Implementation Bug (prod code issue), Test Bug (incorrect test logic), Environment Issue (infrastructure/config), Flaky Test (non-deterministic), or Breaking Change (intentional API change). Provides detailed debugging context with file locations, line numbers, expected vs actual behavior, and actionable fix recommendations. Identifies failure patterns across test suite to suggest systemic improvements.
Coverage Analysis
Measures and reports code coverage with unit test target ≥80%, integration test target ≥70%, and critical path requirement 100%. Identifies untested code paths, edge cases, and coverage regressions. Generates detailed coverage reports with trend analysis and gap identification.
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 · 107 lines · 16 tokens per session scan A 5629384732ab
test-runner is an agent published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 990 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
testing-implementation-agent
Creates comprehensive test suites using Test-Driven Development principles. Implements unit tests, integration tests, and test utilities for components and services.
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.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
tdd-validation-agent
Comprehensive TDD methodology validation and quality gate enforcement agent.
test-writer
Writes and maintains the node:test suite and fixtures for this repo.
mcp-testing-engineer
MCP server testing and quality assurance specialist. Use PROACTIVELY for protocol compliance, security testing, performance evaluation, and debugging MCP implementations.