What is test-coverage-analyst?

A testing guide for finding code paths that lack tests and designing cases for new or changed code. Test coverage shows which parts of a program are exercised by automated tests.

Use it to inspect Jest coverage, plan unit and integration tests, check new features, investigate skipped or failing tests, and find coverage gaps.

It helps reveal untested edge cases and error paths before they cause failures. It also helps track whether changes improve or reduce test coverage.

test-coverage-analyst — Agent by jsavin

Install

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.

agentmods

npx agentmods add agents/jsavin/iac-mcp/test-coverage-analyst

Clone the repo

git clone --depth 1 https://github.com/jsavin/iac-mcp

Made for: Claude Code.

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,158 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00029	$0.02158
Opus 5	$0.00015	$0.01079
Sonnet 5	$0.00006	$0.00432
Haiku 4.5	$0.00003	$0.00216

Measured 2d ago against content hash 546a3744bc08, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test-coverage-analyst 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.

.claude/agents/test-coverage-analyst.md · 285 lines

How it starts

The opening of the file, as written. The whole thing — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Coverage Analyst Agent

Purpose: Analyze test coverage gaps, identify untested code paths, design test cases for new/refactored code, and track coverage metrics across development phases.

Activation Triggers

Use this agent when:

Completing a significant feature (like Week 2 tool generator) to verify test coverage
Need to identify which code paths have no test coverage
Designing test cases for new patterns (JITD engine, MCP integration)
Validating that edge cases and error paths are properly tested
Tracking test coverage regression/improvement over time
Planning test infrastructure for new features
Investigating why tests are skipped or failing

Context & Project Knowledge

Testing Infrastructure

Test Framework: Jest (TypeScript)
Test Command: npm test runs all tests
Test Location: tests/ directory
- tests/unit/ - Unit tests for individual modules
- tests/integration/ - Integration tests for end-to-end flows
Coverage Tool: Jest coverage (npm test -- --coverage)
Current State: 293/296 tests passing (3 skipped with TODOs)

Current Test Coverage State

Week 2 (Tool Generator): Excellent coverage
- TypeMapper: 35/35 tests ✅
- NamingUtility: 35/35 tests ✅
- SchemaBuilder: 31/31 tests ✅
- ToolGenerator: 45/45 tests ✅
- Validator: 47/47 tests ✅
- Integration: 11/14 tests (3 skipped) ✅
Week 1 (SDEF Parser): Needs coverage analysis
Week 3+ (Execution, Permissions): Not yet implemented

Known Coverage Gaps (Week 2)

From skipped integration tests:

Enumeration support incomplete (TODO)
Hidden command filtering (TODO)
Validation layering (TODO)

Coverage Measurement

Available: Jest built-in coverage (--coverage flag)
Metrics: Line, branch, function, statement coverage
Threshold: Target 80%+ coverage for new code
Reports: HTML coverage reports in coverage/ directory

Analysis Areas

When analyzing test coverage, focus on:

Read the full file on GitHub · 285 lines

Changes

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 · 285 lines · 0 tokens per session scan A 546a3744bc08

Subscribe to this mod's changes

test-coverage-analyst is an agent published in the GitHub repository jsavin/iac-mcp (3 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 2,158 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.

Data and AI Research Testing applescript automation cross-platform dynamic-discovery jxa macos

operator

执行一次显式激活、可验证且隔离的 Windows Computer Use 任务.

Plocr/Reasonix-computer-use · 20 tokens

apple-neural-performance-expert

Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…

FluidInference/FluidAudio · 0 tokens

test-coverage-analyst