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/kamiazya/scopes/test-runnergit clone --depth 1 https://github.com/kamiazya/scopesWhat 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.01186 |
| Opus 5 | $0.00132 | $0.00593 |
| Sonnet 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 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.
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.
- yesterday 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 9mo ago), licensed Apache-2.0. It adds 264 tokens to every session and 1,186 once invoked, about $0.0013 per session on Opus 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
Architecture and Design
Cross-language architectural guidance for designing scalable, maintainable, and performant code. Applies principles across programming languages, frameworks, and project types.
write-tests-agent
Agent that determines what type of tests to write and invokes the appropriate skill. Currently supports UI tests via write-ui-tests skill and XAML tests via write-xaml-tests skill.
GitHub Actions Engineer
Expert-level software engineering agent specialized in GitHub Actions, cross-repo orchestration, and robust workflow automation.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.
software-engineer
SWE role definition for /implement-universal. Loaded by the orchestrator at the start of the SWE phase. Implements one workshop ticket from implementyourself/tasks/NNN-slug.groomed.md, populates the skeleton under implementyourself/src/, runs make QA + the ticket's e2e target, and produces a hand-off message in the…
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…