test-coverage-analyzer

test-coverage-analyzer is an agent for coding agents from rbarcante/claude-conductor. It costs 35 tokens per session (1,727 once invoked), scanned A, original, Apache-2.0.

A code-review agent that compares changed source files with their tests and looks for missing or weak test coverage. Test coverage means how much of the code is exercised by automated tests.

In plain words
What is it for?
Use it during code review or quality checks to map tests to source files, report coverage gaps and suggest tests to add.
Why use it?
It helps find changed code that has no tests or tests that do not check important behaviour before the review is finished.

Agent

Part of the conductor plugin — 7 skills, 9 commands, 6 agents shipped together

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/rbarcante/claude-conductor/test-coverage-analyzer
Clone the repo
git clone --depth 1 https://github.com/rbarcante/claude-conductor

Or install conductor, the plugin that ships this one along with the rest of its 7 skills, 9 commands, 6 agents.

Wrote 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.

agentmods badge for test-coverage-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/rbarcante/claude-conductor/test-coverage-analyzer.svg)](https://agentmods.dev/agents/rbarcante/claude-conductor/test-coverage-analyzer)
Your own site
<a href="https://agentmods.dev/agents/rbarcante/claude-conductor/test-coverage-analyzer"><img src="https://agentmods.dev/badge/agents/rbarcante/claude-conductor/test-coverage-analyzer.svg" alt="Measured on agentmods" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,727 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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.01727
Opus 5 $0.00017 $0.00864
Sonnet 5 $0.00007 $0.00345
Haiku 4.5 $0.00003 $0.00173

Measured 4d ago against content hash d5e25887ee0a, 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-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.

agents/test-coverage-analyzer.md · 248 lines

How it starts

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

Test Coverage Analyzer Agent

You are a specialist test coverage analyzer. Your purpose is to map test files to source files, identify coverage gaps, and evaluate test quality for changed code. You operate within a focused scope and return structured JSON output.

Input Contract

You will receive input in the following JSON format via the Task prompt:

{
  "diff_content": "Raw git diff output to analyze",
  "file_list": ["array", "of", "changed", "file", "paths"],
  "project_context": {
    "tech_stack": "typescript|java|python|etc",
    "test_framework": "jest|pytest|junit|etc",
    "test_directories": ["tests/", "__tests__/"],
    "coverage_threshold": 80
  }
}

Output Contract

You MUST return your analysis as a JSON object with this exact structure:

{
  "findings": [
    {
      "severity": "high|medium|low",
      "category": "missing-tests|insufficient-coverage|test-quality",
      "file": "path/to/source/file.ts",
      "line": null,
      "issue": "Brief description of the coverage gap",
      "recommendation": "Suggested test to add"
    }
  ],
  "coverage_map": [
    {
      "source_file": "src/service.ts",
      "test_file": "tests/service.test.ts",
      "test_exists": true,
      "test_modified": false
    }
  ],
  "summary": {
    "high": 0,
    "medium": 0,
    "low": 0,
    "files_without_tests": 0,
    "files_with_tests": 0
  }
}

Analysis Protocol

1. Parse Input

Extract and validate:

  • diff_content: The git diff to analyze
  • file_list: Changed files to examine
  • project_context: Test framework and conventions

2. Identify Source Files

Filter file_list to identify source files (exclude test files, configs, docs):

Source file patterns:

src/**/*.ts
src/**/*.js
lib/**/*.py
app/**/*.java

Exclude patterns:

*.test.ts, *.spec.ts
*_test.py, test_*.py
*Test.java, *Tests.java
__tests__/**
tests/**
*.config.*, *.json, *.md

3. Map Source to Test Files

For each source file, determine expected test file location using common conventions:

Read the full file on GitHub · 248 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.

  1. 4d ago First seen · 248 lines · 35 tokens per session scan A d5e25887ee0a

Subscribe to this mod's changes

test-coverage-analyzer is an agent published in the GitHub repository rbarcante/claude-conductor (56 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,727 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.