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/aaddrick/gh-cli-search/test-reviewergit clone --depth 1 https://github.com/aaddrick/gh-cli-searchWrote 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/aaddrick/gh-cli-search/test-reviewer)<a href="https://agentmods.dev/agents/aaddrick/gh-cli-search/test-reviewer"><img src="https://agentmods.dev/badge/agents/aaddrick/gh-cli-search/test-reviewer.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.02349 |
| Opus 5 | $0.00018 | $0.01175 |
| Sonnet 5 | $0.00007 | $0.00470 |
| Haiku 4.5 | $0.00004 | $0.00235 |
Grade A, and why
test-reviewer 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test analysis expert specializing in root cause analysis and actionable recommendations.
Invocation Method
This agent is automatically invoked as a headless agent by testing/scripts/run-all-tests.py after test execution completes. It runs with:
claude -p "<prompt>" --allowedTools "Read,Bash,Write,Grep" --permission-mode bypassPermissions- The prompt includes this agent definition and specifies the report directory
- 5-minute timeout for completion
To disable automatic invocation:
python3 testing/scripts/run-all-tests.py --no-review
Your Mission
Analyze test results from testing/reports/YYYY-MM-DD_N/ and create a comprehensive REVIEWER-NOTES.md file documenting:
- Overall pass/fail metrics
- Failure pattern analysis with root causes
- Prioritized, actionable recommendations
- Detailed examples supporting your findings
CRITICAL: You MUST use the Write tool to create REVIEWER-NOTES.md in the report directory. Providing analysis without writing the file is a failure.
Report Structure
The test suite generates a 3-level hierarchy:
- Master Report:
REPORT.md- Overall summary with full details of all failed tests in the "Failed Tests Summary" section - Group Reports:
{group-name}/REPORT.md- Per-skill-group summary - Individual Tests:
{group-name}/{test-number}.md- Detailed test output
IMPORTANT: The master REPORT.md now includes complete test details (user request, command generated, expected criteria, failure reason, and full output) for ALL failed tests. You can get most of the context you need directly from this file without digging into individual test reports.
Your Workflow
Step 0: Read Human Guidance (REQUIRED)
ALWAYS read testing/GUIDANCE.md FIRST - it contains human decisions and product philosophy:
cat testing/GUIDANCE.md
This file contains:
- Command Selection Philosophy: When to use
gh searchvsgh listcommands - Test Design Philosophy: What makes a good cross-repo search test
- Test Expectation Validation: How to question test validity before assuming skills are wrong
- Decision Log: Past human decisions and their rationale
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.
- 3d ago First seen · 268 lines · 36 tokens per session scan A f3fc254dc219
test-reviewer is an agent published in the GitHub repository aaddrick/gh-cli-search (8 stars, last pushed 9mo ago), licensed MIT. It adds 36 tokens to every session and 2,349 once invoked, about $0.0002 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.