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.
npx agentmods add skills/juanmhidalgo/claude-plugins/coverage-gatenpx skills add juanmhidalgo/claude-plugins --skill coverage-gategit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/juanmhidalgo/claude-plugins/coverage-gate)<a href="https://agentmods.dev/skills/juanmhidalgo/claude-plugins/coverage-gate"><img src="https://agentmods.dev/badge/skills/juanmhidalgo/claude-plugins/coverage-gate.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.01148 |
| Opus 5 | $0.00016 | $0.00574 |
| Sonnet 5 | $0.00007 | $0.00230 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
coverage-gate 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GHA Threshold Detection
Search .github/workflows/*.yml for coverage actions and extract thresholds.
Supported Actions
| Action | Threshold Fields | Format |
|---|---|---|
orgoro/coverage |
thresholdAll, thresholdNew, thresholdModified |
Decimal 0-1 (multiply by 100) |
irongut/CodeCoverageReport |
thresholds |
'60 80' (warning failure) — use failure value |
5monkeys/cobertura-action |
minimum_coverage |
Integer 0-100 |
codecov/codecov-action |
None inline — check codecov.yml at repo root |
target: 80% |
Detection Steps
- Glob for
.github/workflows/*.yml - Grep for coverage action patterns
- Read the matching workflow file
- Extract threshold values from
with:block - Normalize all thresholds to percentages (0-100 scale)
If no coverage config found: Skip the coverage gate entirely with a note.
Default thresholds (when action exists but thresholds are partially configured):
thresholdAll: 55%thresholdNew: 80%thresholdModified: 65%
File Categorization
Map GHA categories to git state:
| Category | PR Context | Staged Context |
|---|---|---|
| New files | git diff --name-only --diff-filter=A <base>...HEAD |
git diff --cached --name-only --diff-filter=A |
| Modified files | git diff --name-only --diff-filter=M <base>...HEAD |
git diff --cached --name-only --diff-filter=M |
| All files | Overall coverage report | Overall coverage report |
Filter to source files only — exclude test files, configs, docs, migrations, __init__.py.
Coverage Tool Detection
Detect the project's coverage tool. Check the GHA workflow first — it reveals the exact command and flags.
| Ecosystem | Config Files | Coverage Command | Report |
|---|---|---|---|
| Python (pytest-cov) | pyproject.toml, setup.cfg |
pytest --cov --cov-report=xml |
coverage.xml |
| Python (coverage.py) | .coveragerc |
coverage run -m pytest && coverage xml |
coverage.xml |
| Node (jest) | package.json |
npx jest --coverage --coverageReporters=cobertura |
coverage/cobertura-coverage.xml |
| Node (vitest) | vitest.config.* |
npx vitest run --coverage |
coverage/cobertura-coverage.xml |
| Go | go.mod |
go test -coverprofile=coverage.out ./... |
coverage.out |
What ships with it
1 file 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.
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.
- 6d ago First seen · 100 lines · 33 tokens per session scan A b4a340ecd14d
coverage-gate is a skill published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 11d ago), licensed MIT. It adds 33 tokens to every session and 1,148 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-31.
Other skills, from other repositories
Karma Testing
Comprehensive Karma test runner skill for browser-based JavaScript unit testing with Jasmine, Mocha, or QUnit frameworks, real browser execution, coverage reporting, and CI/CD pipeline integration.
AI Release Guardian
Analyze a git diff, map affected risks, select the tests that matter, detect coverage gaps on changed lines, run configurable quality gates, and produce a go/no-go release report with cited evidence. Recommends only; never merges or deploys.
Code Coverage Analysis
Measure and enforce test coverage with Istanbul/nyc, c8, Jest, and Vitest. Covers branch versus line coverage, per-directory thresholds, CI gates, and correctly excluding generated code from reports.
frontmcp-testing
Use for anything about testing FrontMCP servers: writing or running unit, integration, and E2E tests and reaching the 95%+ coverage bar. Covers Jest setup and coverage gating; unit-testing a ToolContext execute() with mock context, inputs, and Zod schema validation; testing resources and prompts; in-memory testing via…
Code Coverage with gcov
Add gcov code coverage instrumentation to C/C++ projects.
Line Execution Checker
Check if specific lines were executed using gcov data.