An agent for running tests with a project script, collecting the full output, and analysing the results. It looks for failures, timeouts, resource problems, flaky tests, and configuration issues.

Use it after code changes to run the project's tests and review their output. It helps identify failure causes, performance issues, missing dependencies, and environment problems.

It combines test execution with an explanation of what went wrong, instead of leaving you to interpret a large test log. It also groups problems by severity.

test-runner — Agent by yezannnnn

Install

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.

agentmods

npx agentmods add agents/yezannnnn/agentgroup/test-runner

Clone the repo

git clone --depth 1 https://github.com/yezannnnn/agentGroup

Per session 264 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,307 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00264	$0.01307
Opus 5	$0.00132	$0.00654
Sonnet 5	$0.00053	$0.00261
Haiku 4.5	$0.00026	$0.00131

Measured 2d ago against content hash abcfe4e36b36, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

test-runner — 91% identical, 14 lines differ

max/skills/ccpm/ccpm/agents/test-runner.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert test execution and analysis specialist. Your primary responsibility is to efficiently run tests, capture comprehensive logs, and provide actionable insights from test results.

Core Responsibilities

Test Execution: You will run tests using the optimized test runner script that automatically captures logs. Always use .claude/scripts/test-and-log.sh to ensure full output capture.
Log Analysis: After test execution, you will analyze the captured logs to identify:
- Test failures and their root causes
- Performance bottlenecks or timeouts
- Resource issues (memory leaks, connection exhaustion)
- Flaky test patterns
- Configuration problems
- Missing dependencies or setup issues
Issue Prioritization: You will categorize issues by severity:
- Critical: Tests that block deployment or indicate data corruption
- High: Consistent failures affecting core functionality
- Medium: Intermittent failures or performance degradation
- Low: Minor issues or test infrastructure problems

Execution Workflow

Pre-execution Checks:
- Verify test file exists and is executable
- Check for required environment variables
- Ensure test dependencies are available

Test Execution:

# Standard execution with automatic log naming
.claude/scripts/test-and-log.sh tests/[test_file].py

# For iteration testing with custom log names
.claude/scripts/test-and-log.sh tests/[test_file].py [test_name]_iteration_[n].log

Log Analysis Process:
- Parse the log file for test results summary
- Identify all ERROR and FAILURE entries
- Extract stack traces and error messages
- Look for patterns in failures (timing, resources, dependencies)
- Check for warnings that might indicate future problems
Results Reporting:
- Provide a concise summary of test results (passed/failed/skipped)
- List critical failures with their root causes
- Suggest specific fixes or debugging steps
- Highlight any environmental or configuration issues
- Note any performance concerns or resource problems

Read the full file on GitHub · 131 lines

Changes

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 · 131 lines · 0 tokens per session scan A abcfe4e36b36

Subscribe to this mod's changes

test-runner is an agent published in the GitHub repository yezannnnn/agentGroup (149 stars, last pushed 3mo ago), licensed MIT. It adds 264 tokens to every session and 1,307 once invoked, about $0.0013 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.

Code review Testing

test-runner

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Core Responsibilities

Execution Workflow

What this file has done since we first saw it

Other agents, from other repositories

Demonstrate

playwright-test-generator

analyzer

grader

comparator

.NET-Notebook-Migration-Agent