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 skills add parisgroup-ai/imersao-ia-setup --skill coverage-reportgit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/coverage-report)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/coverage-report"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/coverage-report/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.
<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/coverage-report"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/coverage-report.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.02076 |
| Opus 5 | $0.00026 | $0.01038 |
| Sonnet 5 | $0.00010 | $0.00415 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade A, and why
coverage-report 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.
How it starts
The opening of the file, as written. The whole thing — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
coverage-report
Generate comprehensive coverage reports with historical data and trend analysis.
Commands
/coverage-report # Current + 7-day trend
/coverage-report --full # Full report with all gaps
/coverage-report --compare # Compare branch vs main
/coverage-report --trend 30 # 30-day trend analysis
Execution Flow
1. Load History
cat .coverage-history/snapshots.jsonl
Parse all snapshots into array for analysis. Each line is a JSON object.
2. Calculate Current State
From latest snapshot (last line):
tail -1 .coverage-history/snapshots.jsonl | jq .
Extract:
- Vitest: lines, branches, functions
- Playwright: routes covered / total
- pytest: lines, branches
3. Calculate Trends
7-day trend (default):
# Get snapshot from 7 days ago
WEEK_AGO=$(date -v-7d +%Y-%m-%d)
grep "\"ts\":\"$WEEK_AGO" .coverage-history/snapshots.jsonl | tail -1
30-day trend (with --trend 30):
MONTH_AGO=$(date -v-30d +%Y-%m-%d)
grep "\"ts\":\"$MONTH_AGO" .coverage-history/snapshots.jsonl | tail -1
Trend indicators:
| Delta | Indicator |
|---|---|
| > +0.5% | ↑ (improving) |
| -0.5% to +0.5% | → (stable) |
| < -0.5% | ↓ (declining) |
4. Load Critical Gaps History
cat .coverage-history/critical-gaps.jsonl
Track persistence:
- New: First seen in current snapshot
- Persistent: Seen in multiple snapshots (calculate days)
- Resolved: Was in history, now meets threshold
5. Cross-Reference E2E Plan
Load E2E coverage plan for progress tracking:
cat docs/plans/e2e-coverage-plan.md
Extract phase targets and compare with current Playwright coverage.
6. Generate ASCII Trend Chart
For the trend visualization:
Lines Coverage (7 days)
75% │ ╭──●
│ ╭───╯
70% │ ╭───╯
│ ──╯
65% │
└─────────────────
28 29 30 31 01 02 03 04
Algorithm:
- Get all snapshots in date range
- Find min/max coverage values
- Scale to 5 rows (height)
- Plot each day's value
- Connect with box-drawing characters (─, │, ╭, ╯, ●)
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.
- 11d ago First seen · 272 lines · 52 tokens per session scan A 56200d629ed5
coverage-report is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 28d ago), licensed MIT. It adds 52 tokens to every session and 2,076 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.
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…
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"…
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…
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.
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?".
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".