test-coverage-analyzer

test-coverage-analyzer is a skill for Claude Code, Codex from armanzeroeight/fastagent-plugins. It costs 37 tokens per session (801 once invoked), scanned A, original, MIT.

A guide that examines test coverage reports, which show how much of a program's code tests execute, and highlights missing tests.

In plain words
What is it for?
Use it to review line, branch, function, and statement coverage in JavaScript, Python, or Go projects.
Why use it?
It turns coverage numbers into a prioritized list of testing gaps instead of leaving developers to inspect reports manually.

Skill for Claude CodeCodex

Part of the testing-toolkit plugin — 2 skills 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 skills/armanzeroeight/fastagent-plugins/test-coverage-analyzer
Any agent
npx skills add armanzeroeight/fastagent-plugins --skill test-coverage-analyzer
Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins

Made for: Claude Code, Codex.

Or install testing-toolkit, the plugin that ships this one along with the rest of its 2 skills.

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/skills/armanzeroeight/fastagent-plugins/test-coverage-analyzer.svg)](https://agentmods.dev/skills/armanzeroeight/fastagent-plugins/test-coverage-analyzer)
Your own site
<a href="https://agentmods.dev/skills/armanzeroeight/fastagent-plugins/test-coverage-analyzer"><img src="https://agentmods.dev/badge/skills/armanzeroeight/fastagent-plugins/test-coverage-analyzer.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 801 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.00037 $0.00801
Opus 5 $0.00018 $0.00400
Sonnet 5 $0.00007 $0.00160
Haiku 4.5 $0.00004 $0.00080

Measured yesterday against content hash 411718f65ee1, 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 yesterday.

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.

plugins/testing-toolkit/skills/test-coverage-analyzer/SKILL.md · 143 lines

How it starts

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

Test Coverage Analyzer

Analyze test coverage and identify testing gaps.

Quick Start

Run coverage and analyze results:

# JavaScript/TypeScript
npm test -- --coverage

# Python
pytest --cov=src --cov-report=term-missing

# Go
go test -cover ./...

Instructions

Step 1: Generate Coverage Report

JavaScript/TypeScript (Jest):

npm test -- --coverage --coverageReporters=text --coverageReporters=lcov

JavaScript/TypeScript (Vitest):

vitest run --coverage

Python (pytest):

pytest --cov=src --cov-report=html --cov-report=term-missing

Go:

go test -coverprofile=coverage.out ./...
go tool cover -html=coverage.out

Step 2: Analyze Coverage Metrics

Review these key metrics:

  • Line coverage: Percentage of lines executed
  • Branch coverage: Percentage of conditional branches tested
  • Function coverage: Percentage of functions called
  • Statement coverage: Percentage of statements executed

Target thresholds:

  • Critical code: 80%+ coverage
  • Standard code: 60%+ coverage
  • UI/Config: 40%+ coverage

Step 3: Identify Gaps

Look for:

  • Uncovered functions: Functions with 0% coverage
  • Partial coverage: Functions with <50% coverage
  • Missing branches: Untested if/else paths
  • Error paths: Untested catch blocks
  • Edge cases: Boundary conditions not tested

Step 4: Prioritize Testing

High Priority (test first):

  • Business logic with 0% coverage
  • Security-critical functions
  • Payment/transaction code
  • Data validation logic
  • Error handling paths

Medium Priority (test next):

  • API endpoints
  • Database operations
  • Utility functions
  • Configuration logic

Low Priority (test if time permits):

  • Simple getters/setters
  • UI presentation logic
  • Type definitions
  • Generated code

Step 5: Create Action Plan

For each gap:

  1. Identify the untested code
  2. Determine test type needed (unit/integration/e2e)
  3. Estimate effort (small/medium/large)
  4. Assign priority (high/medium/low)
  5. Create test implementation tasks

Read the full file on GitHub · 143 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. yesterday First seen · 143 lines · 37 tokens per session scan A 411718f65ee1

Subscribe to this mod's changes

test-coverage-analyzer is a skill published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 801 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

eliza-cloud

Use when the task involves Eliza Cloud or elizaOS Cloud as a managed backend, app platform, deployment target, billing layer, or monetization surface. The catch-all skill for any user request about THEIR existing apps / containers / earnings / credits / api-keys / analytics / billing / payment requests / payouts …

elizaOS/eliza · 191 tokens

build-monetized-app

Use when the task is building a new app on Eliza Cloud that earns money — chat apps, agent apps, MCP-backed tools, anything that calls the cloud's chat/messages/inference endpoints on behalf of users. Covers app registration, container deploy, markup configuration, affiliate header, app charge requests, x402 payment…

elizaOS/eliza · 126 tokens

contribute-to-eliza

Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…

elizaOS/eliza · 68 tokens

discord

Use when you need to control Discord from Otto via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, set bot presence/activity, or handle moderation actions in…

elizaOS/eliza · 70 tokens

eliza-cloud-buy-domain

Use whenever a user wants to register or buy a custom domain for an Eliza Cloud app — including in the same request as building the app ("build me X and put it on Y.com"). Uses Cloudflare as registrar after explicit user confirmation, paid from the user's existing cloud credit balance. Pairs with build-monetized-app…

elizaOS/eliza · 125 tokens

notion

Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.

elizaOS/eliza · 69 tokens