find-coverage-gaps

find-coverage-gaps is a skill for Claude Code from tomzx/agents. It costs 30 tokens per session (1,858 once invoked), scanned A, original, MIT.

A test-coverage scanner that finds code with little or no test coverage and ranks it using how often it changes and how complex it is.

In plain words
What is it for?
Use it to decide which files and modules should receive tests first, using tools such as pytest, Jest, Vitest, Go tests, or Tarpaulin.
Why use it?
It helps distinguish minor coverage gaps from untested code that poses a greater production risk.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Good fit Use it to decide which files and modules should receive tests first, using tools such as pytest, Jest, Vitest, Go tests, or Tarpaulin.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tomzx/agents/find-coverage-gaps
View source ↗ tomzx/agents
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.

Any agent
npx skills add tomzx/agents --skill find-coverage-gaps
Clone the repo
git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

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 find-coverage-gaps

README.md
[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/find-coverage-gaps.svg)](https://agentmods.dev/skills/tomzx/agents/find-coverage-gaps)
Your own site
<a href="https://agentmods.dev/skills/tomzx/agents/find-coverage-gaps"><img src="https://agentmods.dev/badge/skills/tomzx/agents/find-coverage-gaps.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,858 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 47
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 209
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 53
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
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.1 $0.00030 $0.01858
Opus 5 $0.00015 $0.00929
Sonnet 5 $0.00006 $0.00372
Haiku 4.5 $0.00003 $0.00186

Measured 4d ago against content hash 09bce972ec2c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

find-coverage-gaps 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.

skills/find-coverage-gaps/SKILL.md · 211 lines

How it starts

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

TODAY=!date +%Y-%m-%d

Coverage Gaps

Finds the parts of the codebase with the least test coverage, then ranks them by churn and complexity so the most important gaps surface first. Low coverage in a stable file is a minor concern; low coverage in a file that changes constantly and is hard to understand is a production risk.

Prerequisites

  • Working directory is the root of the repository
  • Optional: $1 — path to limit the scan (defaults to .)
  • Tests must be runnable; coverage data is generated by running the test suite
  • Language-specific tools:
    • Python: pytest-cov (uv add --dev pytest-cov)
    • JavaScript/TypeScript: jest --coverage or vitest --coverage
    • Go: go test -cover ./...
    • Rust: cargo tarpaulin (cargo install cargo-tarpaulin)

Coverage Thresholds

Coverage Status
≥ 80% Acceptable
50–79% 🟡 Gap — schedule tests
< 50% 🔴 Critical gap — prioritize
0% 🔴 No tests at all

Files below threshold are ranked by a risk score: (1 - coverage) × churn_commits × complexity_score.

Steps

1. Run the Test Suite with Coverage

Python:

python -m pytest ${1:-.} --cov=${1:-.} --cov-report=term-missing --cov-report=json:coverage.json -q 2>&1 | tail -40

JavaScript/TypeScript — Jest:

npx jest --coverage --coverageReporters=json-summary --coverageDirectory=.coverage 2>/dev/null
cat .coverage/coverage-summary.json | jq '.[] | select(.lines.pct < 80) | {file: ., pct: .lines.pct}' 2>/dev/null | head -40

JavaScript/TypeScript — Vitest:

npx vitest run --coverage 2>/dev/null

Go:

go test -coverprofile=coverage.out ./... 2>/dev/null && go tool cover -func=coverage.out | rg -v "100.0%" | sort -k3 -n | head -30

Rust:

cargo tarpaulin --out Json --output-dir .coverage 2>/dev/null

2. Parse Coverage Results

Extract per-file coverage percentages from the generated report:

Python — from coverage.json:

python3 -c "
import json, sys
data = json.load(open('coverage.json'))
files = [(v['summary']['percent_covered'], k) for k, v in data['files'].items()]
for pct, f in sorted(files):
    if pct < 80:
        print(f'{pct:5.1f}%  {f}')
" 2>/dev/null

Read the full file on GitHub · 211 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 · 211 lines · 30 tokens per session scan A 09bce972ec2c

Subscribe to this mod's changes

find-coverage-gaps is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 1,858 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-09-03.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens