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/yezannnnn/agentGroupWrote 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/yezannnnn/agentgroup/test-runner)<a href="https://agentmods.dev/agents/yezannnnn/agentgroup/test-runner"><img src="https://agentmods.dev/badge/agents/yezannnnn/agentgroup/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/yezannnnn/agentgroup/test-runner"><img src="https://agentmods.dev/badge/agents/yezannnnn/agentgroup/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.00000 | $0.01307 |
| Opus 5.5 | $0.00000 | $0.00523 |
| Sonnet 5.5 | $0.00000 | $0.00261 |
| Haiku 4.5 | $0.00000 | $0.00131 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-runner — 91% identical, 14 lines differ
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.shto 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
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 · 131 lines · 0 tokens per session scan A abcfe4e36b36
test-runner is an agent published in the GitHub repository yezannnnn/agentGroup (150 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,307 tokens. 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.
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.
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.
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.