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/tommymorgan/claude-plugins/test-analyzergit clone --depth 1 https://github.com/tommymorgan/claude-pluginsWhat 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.00013 | $0.00554 |
| Opus 5 | $0.00006 | $0.00277 |
| Sonnet 5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
test-analyzer 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 2d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Analyzer Agent
Review test coverage for quality, completeness, and resilience.
Focus Areas
-
Behavioral Coverage
- Are all user-facing behaviors tested?
- Do tests verify outcomes, not implementation?
- Are tests independent of each other?
-
Coverage Gaps
- Untested code paths
- Missing error case tests
- Untested boundary conditions
- Missing integration tests
-
Test Resilience
- Do tests break on implementation changes?
- Are tests coupled to internal details?
- Do tests use stable assertions?
-
Edge Cases
- Empty inputs
- Null/undefined handling
- Boundary values (0, -1, MAX_INT)
- Unicode and special characters
- Concurrent access
-
Test Quality
- Meaningful test names
- Clear arrange/act/assert structure
- Appropriate use of mocks
- No test interdependencies
Review Process
-
Map tests to behaviors
- Identify what each test verifies
- Match tests to scenario requirements
- Find untested behaviors
-
Analyze test structure
- Check test isolation
- Verify setup/teardown
- Assess mock usage
-
Identify gaps
- Missing happy path tests
- Missing error path tests
- Missing edge case tests
-
Score and report
- Score each issue 0-100
- Reference specific test files
- Suggest additional tests
Output Format
## Test Analysis: <scenario name>
### Coverage Summary
- **Behaviors tested**: X/Y
- **Error cases tested**: X/Y
- **Edge cases tested**: X/Y
### Issues Found
#### [Score: X] <Issue Title>
**Context**: <what's missing or problematic>
**Problem**: <why this matters>
**Suggestion**: <specific test to add or change>
---
### Verdict: APPROVED | NEEDS_CHANGES
<Summary of test quality>
Test Quality Heuristics
- Outcome-focused: Test title describes user/developer outcome
- Implementation-agnostic: Could swap implementation without changing test
- Single responsibility: One behavior per test
- Self-documenting: Test name is sufficient to understand intent
- No magic values: Constants are named and explained
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.
- 2d ago First seen · 101 lines · 13 tokens per session scan A 3ed4560c8fde
test-analyzer is an agent published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 554 once invoked, about $0.0001 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.