Borrowing it
Nothing to install: this file belongs to kamiazya/scopes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kamiazya/scopes/main/.claude/agents/test-runner.mdgit clone --depth 1 https://github.com/kamiazya/scopesWrote 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/kamiazya/scopes/test-runner)<a href="https://agentmods.dev/agents/kamiazya/scopes/test-runner"><img src="https://agentmods.dev/badge/agents/kamiazya/scopes/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/kamiazya/scopes/test-runner"><img src="https://agentmods.dev/badge/agents/kamiazya/scopes/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.00264 | $0.01186 |
| Opus 5.5 | $0.00106 | $0.00474 |
| Sonnet 5.5 | $0.00053 | $0.00237 |
| Haiku 4.5 | $0.00026 | $0.00119 |
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.
This is a copy
91% identical to test-runner — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 121 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 for the MUXI Runtime system. 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 · 121 lines · 0 tokens per session scan A 724e5c57603d
test-runner is an agent published in the GitHub repository kamiazya/scopes (2 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 264 tokens to every session and 1,186 once invoked, about $0.0011 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to test-runner, differing in 14 lines, and is treated as a copy.
Other agents, from other repositories
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
Playwright Tester Mode
Testing mode for Playwright tests.
sap-screens-reviewer
Adversarial review of a Phase 2 screens.md — checks it describes the LIVE WEB-GUI rendering (accessible names/labels Playwright will use, initial states, dialogs, ALV) and is NOT an ABAP selection-screen/source description. Catches screens.md that was derived from source instead of observed in the browser. Use at the…
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
FAI Deterministic Agent Reviewer
Deterministic Agent reviewer — reproducibility testing, guardrail completeness audit, anti-sycophancy verification, schema validation review, and confidence calibration checks.
FAI AI Search Portal Reviewer
AI Search Portal reviewer — index schema audit, search relevance testing, answer citation accuracy, facet UX review, and performance benchmarking.