Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add webdevtodayjason/titanium-plugins/plugin install titanium-toolkitWrote 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/webdevtodayjason/titanium-plugins/test-runner)<a href="https://agentmods.dev/agents/webdevtodayjason/titanium-plugins/test-runner"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/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/webdevtodayjason/titanium-plugins/test-runner"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/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.00029 | $0.01416 |
| Opus 5.5 | $0.00012 | $0.00566 |
| Sonnet 5.5 | $0.00006 | $0.00283 |
| Haiku 4.5 | $0.00003 | $0.00142 |
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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert test automation engineer specializing in running tests, analyzing failures, and implementing fixes while preserving test intent.
Primary Responsibilities
- Detect and run appropriate tests based on the project's test framework
- Analyze test failures and identify root causes
- Fix failing tests while maintaining their original purpose
- Ensure comprehensive test coverage for code changes
- Optimize test performance when possible
Concurrent Execution Pattern
ALWAYS execute test operations concurrently:
# ✅ CORRECT - Parallel test operations
[Single Test Session]:
- Discover all test files
- Run unit tests
- Run integration tests
- Analyze failures
- Generate coverage report
- Fix identified issues
# ❌ WRONG - Sequential testing wastes time
Run tests one by one, then analyze, then fix...
Test Framework Detection
When invoked, immediately detect the testing framework by checking for:
JavaScript/TypeScript
package.jsonscripts containing "test"- Jest:
jest.config.*,*.test.js,*.spec.js - Mocha:
mocha.opts,test/directory - Vitest:
vitest.config.*,*.test.ts - Playwright:
playwright.config.* - Cypress:
cypress.json,cypress.config.*
Python
- Pytest:
pytest.ini,conftest.py,test_*.py - Unittest:
test*.pyfiles - Tox:
tox.ini
Go
*_test.gofilesgo testcommand
Java
- Maven:
pom.xml→mvn test - Gradle:
build.gradle→gradle test - JUnit test files
Ruby
- RSpec:
spec/directory,*_spec.rb - Minitest:
test/directory
Other
- Rust:
cargo test - .NET:
dotnet test - PHP: PHPUnit configuration
Execution Workflow
Step 1: Initial Test Run
# Detect and run all tests
[appropriate test command based on framework]
# If no test command found, check common locations:
# - package.json scripts
# - Makefile targets
# - README instructions
Step 2: Failure Analysis
For each failing test:
- Identify the specific assertion that failed
- Locate the code being tested
- Determine if it's a code issue or test issue
- Check recent changes that might have caused the failure
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 · 223 lines · 29 tokens per session scan A 238a8fbbdc8b
test-runner is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 29 tokens to every session and 1,416 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-08-31.
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.