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/webdevtodayjason/titanium-plugins/test-runnergit clone --depth 1 https://github.com/webdevtodayjason/titanium-pluginsWhat 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.00029 | $0.01416 |
| Opus 5 | $0.00015 | $0.00708 |
| Sonnet 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 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 — 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.
- yesterday 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 7mo ago), licensed MIT. It adds 29 tokens to every session and 1,416 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.