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/laurigates/claude-plugins/configure-coveragenpx skills add laurigates/claude-plugins --skill configure-coveragegit clone --depth 1 https://github.com/laurigates/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/laurigates/claude-plugins/configure-coverage)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/configure-coverage"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/configure-coverage.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 | $0.00040 | $0.01855 |
| Opus 5 | $0.00020 | $0.00928 |
| Sonnet 5 | $0.00008 | $0.00371 |
| Haiku 4.5 | $0.00004 | $0.00186 |
Grade A, and why
configure-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 today.
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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/configure:coverage
Check and configure code coverage thresholds and reporting for test frameworks.
When to Use This Skill
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up coverage thresholds for Vitest, Jest, pytest, or Rust | Running tests with coverage (/test:coverage) |
| Configuring coverage reporters (text, JSON, HTML, lcov) | Configuring the test framework itself (/configure:tests) |
| Adding Codecov or Coveralls integration to CI/CD | Analyzing test failures (test-runner agent) |
| Auditing coverage configuration compliance across a project | Writing individual test cases |
| Adjusting coverage threshold percentages | Configuring general CI/CD workflows (/configure:workflows) |
Context
- Project root: !
pwd - Package files: !
find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' \) - Vitest config: !
find . -maxdepth 1 -name 'vitest.config.*' - Jest config: !
find . -maxdepth 1 -name 'jest.config.*' - Coverage dir: !
find . -maxdepth 1 -type d -name 'coverage' - Codecov config: !
find . -maxdepth 1 \( -name 'codecov.yml' -o -name '.codecov.yml' \) - Project standards: !
find . -maxdepth 1 -name '.project-standards.yaml'
Parameters
Parse from command arguments:
--check-only: Report compliance status without modifications (CI/CD mode)--fix: Apply fixes automatically without prompting--threshold <percentage>: Set coverage threshold (default: 80)
Default threshold: 80% (lines, branches, functions, statements)
Supported frameworks:
- Vitest:
@vitest/coverage-v8or@vitest/coverage-istanbul - Jest: Built-in coverage with
--coverage - pytest:
pytest-covplugin - Rust:
cargo-llvm-covorcargo-tarpaulin
Execution
Execute this code coverage compliance check:
Step 1: Detect test framework and coverage configuration
Check for framework indicators:
| Indicator | Framework | Coverage Tool |
|---|---|---|
vitest.config.* with coverage |
Vitest | @vitest/coverage-v8 |
jest.config.* with coverage |
Jest | Built-in |
pyproject.toml [tool.coverage] |
pytest | pytest-cov |
.cargo/config.toml with coverage |
Rust | cargo-llvm-cov |
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.
- today First seen · 204 lines · 40 tokens per session scan A 69d02cd48404
configure-coverage is a skill published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,855 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.
Other skills, from other repositories
phpunit-migration-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-unit-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-test-adversarial-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
phpunit-integration-to-unit-migrating
Use this skill ONLY when the user explicitly requests an audit, migration, or evaluation of whether a Shopware integration test belongs in the unit suite — trigger phrases like "audit integration tests", "migrate integration tests to unit", "is this an integration test or a unit test", "evaluate integration tests for…
phpunit-unit-test-writing
Use this skill when the user asks to write, generate, create, or add PHPUnit unit tests for a Shopware 6 source class — phrases like "write unit tests for X", "generate tests for ClassName", "create PHPUnit tests", "add test coverage", "test this class", "cover this with tests", "I need tests for", "unit test this"…