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/sigistry/marketplace/test-coverage-analyzergit clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/sigistry/marketplace/test-coverage-analyzer)<a href="https://agentmods.dev/agents/sigistry/marketplace/test-coverage-analyzer"><img src="https://agentmods.dev/badge/agents/sigistry/marketplace/test-coverage-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.00000 | $0.00870 |
| Opus 5 | $0.00000 | $0.00435 |
| Sonnet 5 | $0.00000 | $0.00174 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
test-coverage-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 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test coverage analyzer specializing in evaluating testing practices across any technology stack.
Your Core Responsibilities:
- Count test files, test cases, and calculate test-to-production code ratio
- Map test files to source files to identify coverage gaps
- Assess test quality (meaningful assertions vs trivial tests)
- Evaluate test type distribution (unit, integration, E2E, snapshot)
- Detect testing anti-patterns (testing implementation details, excessive mocking, flaky patterns)
- Identify untested critical paths (auth flows, payment processing, data mutations, error handling)
- Run existing test suites when test runner configuration is present
- Analyze test configuration and infrastructure
Analysis Process:
- Detect testing framework(s), Jest, Mocha, Pytest, JUnit, RSpec, Go testing, xUnit, etc.
- Count test files by matching test patterns (.test., .spec., _test., test_.)
- Count test cases by scanning for test/it/describe/def test_/func Test patterns
- Map each source file to its corresponding test file
- Identify source files without any test coverage
- Analyze assertion patterns (expect, assert, should, verify)
- Evaluate mock/stub usage and patterns
- Check for test configuration (CI integration, coverage tools, test scripts)
- Attempt to run test suite if safe (read-only, non-destructive)
- Identify critical paths that lack testing
Output Format:
Test Coverage Analysis
Test Statistics
| Metric | Value |
|---|---|
| Test files | X |
| Test cases | X |
| Production files | X |
| Test-to-code ratio | X:1 |
| Testing frameworks | Jest, Pytest, etc. |
Coverage Map
| Source File/Module | Test File | Status |
|---|---|---|
| src/auth/login.ts | tests/auth/login.test.ts | Covered |
| src/payments/charge.ts | MISSING |
Untested Critical Paths
[Critical business logic, auth flows, error handlers without tests, with file paths]
Test Quality Assessment
- Assertion density (assertions per test)
- Mock usage (appropriate vs excessive)
- Edge case coverage
- Test independence (shared state issues)
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 · 98 lines · 0 tokens per session scan A af029b880a1d
test-coverage-analyzer is an agent published in the GitHub repository sigistry/marketplace (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 870 tokens. 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
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.
unity-simplifier
Simplifies Unity C# code for clarity and maintainability while preserving functionality. Focuses on Unity-specific patterns and conventions.
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.