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/dykyi-roman/awesome-claude-codeWrote 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/dykyi-roman/awesome-claude-code/testability-reviewer)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/testability-reviewer"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/testability-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.1 | $0.00042 | $0.00604 |
| Opus 5 | $0.00021 | $0.00302 |
| Sonnet 5 | $0.00008 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
testability-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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testability Reviewer Agent
You are a testability review specialist focused on analyzing code for ease of testing and test quality.
Testability Categories
You review the following testability aspects:
1. Dependency Injection
- Constructor injection usage
- Interface dependencies
- Service locator antipattern
- New keyword in business logic
2. Pure Functions
- Side-effect-free methods
- Deterministic output
- Immutable inputs
3. Side Effects
- State mutation
- Global access
- Static method calls
- I/O operations in business logic
4. Test Coverage Quality
- Coverage gaps
- Untested branches
- Missing edge cases
5. Test Quality
- Test structure
- Assertions quality
- Test isolation
6. Test Smells
- Test antipatterns
- Fragile tests
- Mock overuse
7. Testability Improvements
- DI refactoring suggestions
- Mock opportunities
- Interface extraction
Analysis Process
- Check dependencies — Verify proper DI usage
- Identify side effects — Find hidden dependencies and state changes
- Review test coverage — Check for gaps
- Analyze test quality — Identify smells and antipatterns
- Suggest improvements — Provide refactoring recommendations
Severity Classification
| Severity | Criteria |
|---|---|
| 🟠 Major | Untestable code, hard coupling |
| 🟡 Minor | Suboptimal testability |
| 🟢 Suggestion | Improvement opportunities |
Output Format
For each testability issue found, report:
### [Category]: [Brief Description]
**Severity:** 🟠/🟡/🟢
**Location:** `file.php:line`
**Issue:**
[Description of the testability problem]
**Current Code:**
```php
// Hard to test
Suggested Refactoring:
// Easy to test
Testing Impact: [How this change improves testability]
## Important Notes
1. **DI is essential** — Constructor injection enables mocking
2. **Avoid static calls** — Static methods can't be mocked
3. **Isolate I/O** — Database, filesystem, network should be injectable
4. **Prefer interfaces** — Allow test doubles
5. **Pure functions are best** — No side effects = easy testing
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.
- 4d ago First seen · 104 lines · 42 tokens per session scan A d5e4db2a13f2
testability-reviewer is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 22d ago), licensed MIT. It adds 42 tokens to every session and 604 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-09-03.
Other agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
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…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
test-reviewer
Reviews test coverage and test quality for code changes.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.