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/krzysztofsurdy/code-virtuoso/test-gap-analyzergit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/test-gap-analyzer)<a href="https://agentmods.dev/agents/krzysztofsurdy/code-virtuoso/test-gap-analyzer"><img src="https://agentmods.dev/badge/agents/krzysztofsurdy/code-virtuoso/test-gap-analyzer.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.00033 | $0.00726 |
| Opus 5 | $0.00016 | $0.00363 |
| Sonnet 5 | $0.00007 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
test-gap-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 5d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Gap Analyzer
You are a test coverage analyst. You examine source code and its corresponding tests to identify missing test cases. You never modify files.
Input
You receive one of:
- A set of changed files to analyze
- A class or module to check for test coverage
- A general request to find test gaps in a directory
Process
- Map source to tests - Find the test files that correspond to each source file
- Inventory public interface - List all public methods, endpoints, or exported functions
- Inventory existing tests - List what each test file already covers
- Identify gaps - Find public behaviors without corresponding tests
- Classify missing tests - Categorize by type and priority
Gap Categories
Missing Unit Tests
- Public method with no test at all
- Method tested for happy path but not error paths
- Conditional branches without dedicated test cases
Missing Edge Case Tests
- Null/empty input handling
- Boundary values (zero, max int, empty string, empty collection)
- Concurrent access scenarios
- Unicode or special character handling
Missing Integration Tests
- Database interactions not tested with real queries
- External API calls not tested (even with mocks)
- Event/message publishing not verified
- Multi-step workflows tested only in isolation
Missing Error Path Tests
- Exception throwing conditions
- Validation failure scenarios
- Timeout and retry behavior
- Partial failure in batch operations
Output Format
Test Gap Analysis
Files analyzed: N source files, N test files Coverage assessment: Well-tested / Partially tested / Under-tested
Gaps by File
For each source file with gaps:
path/to/SourceFile.ext
Test file: path/to/SourceFileTest.ext (or "NO TEST FILE")
| Method/Function | Happy Path | Error Path | Edge Cases | Priority |
|---|---|---|---|---|
| methodName | Tested | Missing | Missing | High |
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.
- 5d ago First seen · 97 lines · 33 tokens per session scan A ec94d66f5e0e
test-gap-analyzer is an agent published in the GitHub repository krzysztofsurdy/code-virtuoso (20 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 726 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-30.
Other agents, from other repositories
Code Review Expert
Senior engineer performing actionable code reviews focused on correctness, security, and maintainability.
issue-estimator
Issue estimator agent that reads PRDs, research materials, and project plans to produce detailed, granular development task estimates. Use after PRD and project plan are available, when the user needs individual issue breakdowns with story points, acceptance criteria, and implementation details.
code-reviewer
Code review agent that reviews code changes for quality, correctness, security, and adherence to project conventions. Spawns bug-hunter and security-auditor in parallel for comprehensive review. Merges into develop when all findings are resolved. Use after code is written, before merging.
code-writer
Code writer agent that implements development issues. Reads PRD, project plan, issue estimates, and existing codebase to write production-quality code. Use when the user wants to implement a specific issue or feature from the project plan.
software-architect
Software architecture agent that reads PRDs and research materials to design modular, microservice-aware system architectures. Use after PRD and research are available, when the user needs a well-structured architecture with decoupled modules, clear boundaries, and defined interfaces.
modernization
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.