check-coverage

A tool for examining test coverage, meaning which parts of a program's code are exercised by tests. It focuses on shell projects with functions and command-line behavior.

In plain words
What is it for?
Use it to run available coverage checks, connect functions to their tests, identify critical gaps, and produce a report with suggested tests and file locations.
Why use it?
It reveals public functions, error paths, and conditional branches that tests do not cover.

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

Made for: Claude Code, Codex.

Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 320 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.00013 $0.00320
Opus 5 $0.00006 $0.00160
Sonnet 5 $0.00003 $0.00064
Haiku 4.5 $0.00001 $0.00032

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

Security

Grade A, and why

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

What it actually says

Check Coverage

Analyze test coverage and identify gaps.

Workflow

1. Run Coverage (if available)

BASHUNIT_COVERAGE=true ./bashunit tests/

2. Map Functions to Tests

For each file in src/:

# List all public functions
grep "^function bashunit::" src/module.sh

# Find tests referencing each function
grep -r "function_name" tests/

3. Categorize Coverage

  • Well tested — multiple tests, edge cases covered
  • Partially tested — basic test exists, missing edge cases
  • Not tested — no tests found

4. Identify Critical Gaps

Priority 1: Public API functions (export -f) with no tests Priority 2: Error handling paths (return 1, exit 1) not tested Priority 3: Complex conditionals without branch coverage

5. Generate Report

Output a markdown report with:

  • Summary (total functions, tested count, estimated %)
  • Coverage by module
  • Critical gaps with file:line references
  • Recommended tests to add (specific test function names)

Coverage Goals

  • 90%+ for public functions
  • All user-facing CLI commands tested
  • All error paths tested
  • Internal helpers: optional (if trivial)
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. 2d ago First seen · 57 lines · 13 tokens per session scan A 07d7a56c4a92

Subscribe to this mod's changes

check-coverage is a skill published in the GitHub repository TypedDevs/bashunit (424 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 320 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-30.

Related

Other skills, from other repositories

x-nets

Enhanced netstat module with cached data and structured output. View network connections, routing tables, and interface statistics in interactive or TSV/CSV formats. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 69 tokens

x-mankier

Search and browse man pages from ManKier.com. Command line interface for ManKier man page repository. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 62 tokens

x-osv

CLI for Google OSV database. Query vulnerabilities for packages, scan local projects for vulnerable dependencies. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill). Required Tool: Install osv-scanner for project scanning (see https://github.com/google/osv-scanner).

x-cmd/x-cmd · 72 tokens

rule

Skill "rule" from x-cmd/x-cmd, covering rule — rules to rule, 核心命令, 规则文件格式, 示例 and 验证规则文件格式.

x-cmd/x-cmd · 0 tokens

wikipedia

Search and read Wikipedia via x wkp — MediaWiki API, no API key, zero install; query, extract, suggest, and DDG route in one module. Load for wiki, wikipedia, encyclopedia lookup, article summary.

x-cmd/x-cmd · 49 tokens

cve

Look up CVE records via x cve — cached, zero-API-key, daily xz TSV. Load for cve, vulnerability id, kev, epss, nvd, cvelist, or security advisory.

x-cmd/x-cmd · 49 tokens