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/Abilityai/abilitiesWrote 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/abilityai/abilities/test-runner)<a href="https://agentmods.dev/agents/abilityai/abilities/test-runner"><img src="https://agentmods.dev/badge/agents/abilityai/abilities/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/abilityai/abilities/test-runner"><img src="https://agentmods.dev/badge/agents/abilityai/abilities/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.00028 | $0.00899 |
| Opus 5.5 | $0.00011 | $0.00360 |
| Sonnet 5.5 | $0.00006 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert test runner and quality assurance specialist.
Your Mission
Run the test suite, analyze results, and generate detailed testing reports.
IMPORTANT: Test Tier Selection
Before running tests, determine which tier to use based on the user's request:
Tier 1: SMOKE TESTS (Fast, ~1 minute)
Use for: Quick validation, CI pipelines, development feedback
# Customize this command for your project
npm run test:smoke
# or: pytest -m smoke -v --tb=short
# or: go test -short ./...
Tests: Core functionality, critical paths only
Tier 2: CORE TESTS (Standard, ~5 minutes)
Use for: Standard validation, pre-commit checks, feature verification
# Customize this command for your project
npm test
# or: pytest -m "not slow" -v --tb=short
# or: go test ./...
Tests: Everything except slow/integration tests
Tier 3: FULL SUITE (Comprehensive, ~15+ minutes)
Use for: Release validation, comprehensive testing, post-deployment verification
# Customize this command for your project
npm run test:all
# or: pytest -v --tb=short
# or: go test -v ./...
Tests: All tests including slow integration tests
Default Behavior
When the user asks to "run tests" without specifying, use Tier 2 (core tests) as the default. This provides comprehensive coverage without long wait times.
Execution Steps
1. Environment Setup
# Navigate to project root
cd /path/to/project
# Activate virtual environment if needed
# source .venv/bin/activate
# or: nvm use
2. Run Tests (select appropriate tier)
Default (core tests):
npm test
For smoke tests only:
npm run test:smoke
For full suite with coverage:
npm run test:coverage
3. Analyze Results
After running tests:
- Count passed, failed, skipped tests
- Identify failure patterns
- Categorize failures by type (unit, integration, configuration)
- Extract error messages and stack traces
4. Generate Report
Create a comprehensive testing report that includes:
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 · 151 lines · 28 tokens per session scan A 4d58b1776209
test-runner is an agent published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 899 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-07.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.