coverage-run

coverage-run is a skill for Claude Code from parisgroup-ai/imersao-ia-setup. It costs 58 tokens per session (1,409 once invoked), scanned A, original, MIT.

A runner that measures test coverage across JavaScript unit tests, browser tests, and Python tests.

In plain words
What is it for?
Use it to run all coverage checks or only unit, end-to-end, Python, API, or web coverage for a selected part of the project.
Why use it?
It gives you evidence of which parts of the code are exercised by tests instead of relying on guesses.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the imersao plugin — 51 skills, 7 commands shipped together

Good fit Use it to run all coverage checks or only unit, end-to-end, Python, API, or web coverage for a selected part of the project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/parisgroup-ai/imersao-ia-setup/coverage-run
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.

Any agent
npx skills add parisgroup-ai/imersao-ia-setup --skill coverage-run
Clone the repo
git clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setup

Made for: Claude Code.

Or install imersao, the plugin that ships this one along with the rest of its 51 skills, 7 commands.

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 coverage-run

README.md
[![agentmods](https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/coverage-run/github.svg)](https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/coverage-run)
Your own site
<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/coverage-run"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/coverage-run/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for coverage-run

Your own site · 80×15
<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/coverage-run"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/coverage-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,409 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00058 $0.01409
Opus 5 $0.00029 $0.00705
Sonnet 5 $0.00012 $0.00282
Haiku 4.5 $0.00006 $0.00141

Measured 11d ago against content hash 6d336baf9864, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

coverage-run 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 11d 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.

plugins/imersao/skills/coverage-run/SKILL.md · 193 lines

How it starts

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

coverage-run

Execute tests with coverage collection across multiple stacks.

Commands

/coverage-run              # Run all stacks
/coverage-run unit         # Vitest only
/coverage-run e2e          # Playwright only
/coverage-run python       # pytest only
/coverage-run api          # Vitest for packages/api only
/coverage-run web          # Vitest for apps/web only

Execution Flow

1. Read Configuration

cat coverage-config.json

Extract stack commands and report paths from the config.

2. Auto-Detect Stack

Input Stack Command
unit, vitest Vitest pnpm test -- --coverage (turbo passthrough)
e2e, playwright Playwright pnpm -C apps/web test:e2e
python, pytest pytest cd apps/ana-service && pytest --cov
api, database, etc Vitest (scoped) pnpm test --filter="@repo/{name}" -- --coverage
(none) All Run sequentially

Important: Use -- --coverage to pass args through Turborepo to Vitest.

3. Pre-flight Checks

Before running tests:

# Check if DB is accessible (for integration tests)
docker ps | grep postgres || echo "Warning: PostgreSQL not running"

# Check if Python venv exists for pytest
test -d apps/ana-service/.venv || echo "Warning: Python venv not found"

4. Execute Coverage

Vitest (all packages):

# Use -- to pass args through Turborepo
pnpm test -- --coverage --coverage.reporter=json-summary --coverage.reporter=json

Vitest (filtered - recommended):

# Filter to packages with working test scripts
pnpm test --filter="@repo/api" --filter="@repo/database" --filter="@repo/validators" --filter="@repo/logger" -- --coverage --coverage.reporter=json-summary --coverage.reporter=json

Note: Some packages (e.g., @repo/test-utils) have test scripts that don't accept coverage args. Use --filter to exclude them if needed.

Playwright (route coverage - count specs):

# Count specs and calculate route coverage
SPECS=$(find apps/web/e2e/flows -name "*.spec.ts" | wc -l)
TOTAL_ROUTES=216  # from e2e-coverage-plan.md
echo "E2E Coverage: $SPECS specs covering routes"

Read the full file on GitHub · 193 lines

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. 11d ago First seen · 193 lines · 58 tokens per session scan A 6d336baf9864

Subscribe to this mod's changes

coverage-run is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 28d ago), licensed MIT. It adds 58 tokens to every session and 1,409 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-31.

Related

Other skills, from other repositories

improve-code-quality

Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy…

wondelai/skills · 227 tokens

working-with-legacy-code

Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method"…

wondelai/skills · 188 tokens

browser-validator

Automatically validate implementations in real browsers after code is written or when user says "test this", "test what you built in the browser", "check it in a real browser", or "validate at the breakpoints". Uses Chrome DevTools MCP to test responsive breakpoints (320px, 768px, 1024px), check accessibility…

kanopi/cms-cultivator · 99 tokens

test-scaffolding

Automatically generate test scaffolding when user writes new code without tests or mentions needing tests. Supports unit, integration, e2e, and data tests for PHP and JavaScript. Invoke when user mentions "tests", "testing", "coverage", "write tests", or shows new untested code.

kanopi/cms-cultivator · 64 tokens

coverage-analyzer

Automatically analyze test coverage when user asks which code is tested, mentions coverage gaps, or shows code asking about testing. Identifies untested code paths and suggests test additions. Invoke when user asks "what's not tested?", "coverage", "untested code", or "which tests are missing?".

kanopi/cms-cultivator · 63 tokens

test-plan-generator

Automatically generate comprehensive QA test plans when user mentions testing requirements, QA needs, or asks what should be tested. Analyzes code changes and features to create structured test scenarios. Invoke when user mentions "test plan", "QA", "what to test", "testing requirements", or "test scenarios".

kanopi/cms-cultivator · 64 tokens