test-coverage

test-coverage is a skill for Claude Code, Codex from mehdic/bazinga. It costs 60 tokens per session (946 once invoked), scanned A, original, MIT.

A code-review tool that measures which parts of a program are exercised by tests. It supports Python, JavaScript, Go, and Java projects.

In plain words
What is it for?
Use it when reviewing tests, checking a claimed test addition, or deciding whether code meets coverage expectations.
Why use it?
It shows untested code paths and areas with little test coverage before changes are approved or merged.

Skill for Claude CodeCodex

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 skills/mehdic/bazinga/test-coverage
Any agent
npx skills add mehdic/bazinga --skill test-coverage
Clone the repo
git clone --depth 1 https://github.com/mehdic/bazinga

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/mehdic/bazinga/test-coverage.svg)](https://agentmods.dev/skills/mehdic/bazinga/test-coverage)
Your own site
<a href="https://agentmods.dev/skills/mehdic/bazinga/test-coverage"><img src="https://agentmods.dev/badge/skills/mehdic/bazinga/test-coverage.svg" alt="Measured on agentmods" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 946 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.00060 $0.00946
Opus 5 $0.00030 $0.00473
Sonnet 5 $0.00012 $0.00189
Haiku 4.5 $0.00006 $0.00095

Measured 3d ago against content hash 4898f4be75d8, 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 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 3d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/coverage.ps1, scripts/coverage.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/skills/test-coverage/SKILL.md · 151 lines

How it starts

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

Test Coverage Analysis Skill

You are the test-coverage skill. When invoked, you run appropriate coverage tools based on project language and generate structured coverage reports.

When to Invoke This Skill

Invoke this skill when:

  • Tech Lead is reviewing test files
  • Before approving code changes or pull requests
  • Developer claims "added tests"
  • Before merging to main branch
  • Checking if coverage meets project standards

Do NOT invoke when:

  • No tests exist in the project
  • Just viewing code (not reviewing for approval)
  • Emergency hotfix (skip coverage check)
  • Documentation-only changes

Your Task

When invoked:

  1. Execute the test coverage script
  2. Read the generated coverage report
  3. Return a summary to the calling agent

Step 1: Execute Coverage Script

Use the Bash tool to run the pre-built coverage script.

On Unix/macOS:

bash .claude/skills/test-coverage/scripts/coverage.sh

On Windows (PowerShell):

pwsh .claude/skills/test-coverage/scripts/coverage.ps1

Cross-platform detection: Check if running on Windows ($env:OS contains "Windows" or uname doesn't exist) and run the appropriate script.

This script will:

  • Detect project language (Python, JavaScript, Go, Java)
  • Auto-install required tools (pytest-cov, jest, etc.) if needed
  • Run coverage analysis
  • Parse results
  • Generate bazinga/artifacts/{SESSION_ID}/skills/coverage_report.json

Step 2: Read Generated Report

Use the Read tool to read:

bazinga/artifacts/{SESSION_ID}/skills/coverage_report.json

Extract key information:

  • overall_coverage - Total line coverage percentage
  • files_below_threshold - Files with coverage < 80%
  • critical_uncovered_paths - Important code without tests

Step 3: Return Summary

Return a concise summary to the calling agent:

Test Coverage Report:
- Overall coverage: {percentage}%
- Files below 80% threshold: {count} files
- Critical areas with low coverage:
  - {file1}: {percentage}% coverage
  - {file2}: {percentage}% coverage

Details saved to: bazinga/artifacts/{SESSION_ID}/skills/coverage_report.json

Read the full file on GitHub · 151 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 3d ago First seen · 151 lines · 60 tokens per session scan A 4898f4be75d8

Subscribe to this mod's changes

test-coverage is a skill published in the GitHub repository mehdic/bazinga (21 stars, last pushed 7mo ago), licensed MIT. It adds 60 tokens to every session and 946 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens