Borrowing it
Nothing to install: this file belongs to Oolab-labs/patchwork-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Oolab-labs/patchwork-os/main/.claude/skills/ide-coverage/SKILL.mdgit clone --depth 1 https://github.com/Oolab-labs/patchwork-osWrote 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/oolab-labs/patchwork-os/ide-coverage)<a href="https://agentmods.dev/skills/oolab-labs/patchwork-os/ide-coverage"><img src="https://agentmods.dev/badge/skills/oolab-labs/patchwork-os/ide-coverage/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/oolab-labs/patchwork-os/ide-coverage"><img src="https://agentmods.dev/badge/skills/oolab-labs/patchwork-os/ide-coverage.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.00044 | $0.00865 |
| Opus 5.5 | $0.00018 | $0.00346 |
| Sonnet 5.5 | $0.00009 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
ide-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 1mo 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.
This is a copy
94% identical to ide-coverage — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a visual test coverage heatmap and open it in the browser.
This skill uses only built-in tools (Glob, Read, Write, Bash) and works in both IDE-connected and remote sessions.
Arguments
$ARGUMENTS can be:
- A path to a specific coverage file (
coverage/lcov.info,coverage/coverage-summary.json) - A directory to search within (
coverage/) - Empty — auto-discover coverage files in the workspace
Steps
Phase 1 — Locate coverage data
- If
$ARGUMENTSis a specific file path, use it directly. - Otherwise use the Glob tool with patterns:
**/lcov.info,**/coverage-summary.json,**/coverage-final.json(excludenode_modules). - If multiple candidates found, prefer
lcov.info>coverage-summary.json>coverage-final.json. If still ambiguous (multiple projects), list them and ask the user to specify. - If no coverage file found: report "No coverage data found. Run
npm test -- --coverage(or equivalent) first." and stop.
Phase 2 — Parse coverage
- Use the Read tool to read the located coverage file.
- Parse based on format:
- lcov.info: iterate
SF:(source file),LF:(lines found),LH:(lines hit) records →{ file, totalLines, hitLines, pct } - coverage-summary.json (Istanbul/NYC): each key is a file path with
{ lines: { pct, total, covered } } - coverage-final.json: compute line pct from statement map
sand statement mapstatementMap
- lcov.info: iterate
- Build a list:
{ file: string (relative), pct: number, hitLines: number, totalLines: number }[] - Group files by directory for the tree layout. Compute directory-level aggregate coverage.
Phase 3 — Generate and open HTML
- Construct a fully self-contained HTML document (no external URLs — must work from file://) containing:
- A summary header: "Overall coverage: N% · M / K lines covered · P files"
- Color scale: ≥80% =
#22c55e(green), ≥50% =#eab308(yellow), <50% =#ef4444(red), no data =#94a3b8(grey) - A collapsible directory tree using
<details>/<summary>HTML elements (no JS needed for expand/collapse) - Each file as a row:
[coverage bar] filename N% (hitLines/totalLines) - The coverage bar is an inline
<span>with a CSSwidth: N%background — no canvas needed - Directory rows show aggregate coverage for the subtree
- A legend at the top showing the color key
- Clicking a file's name copies its relative path to clipboard (single JS event listener, ~10 lines)
- Page title: "Coverage — "
- Write the HTML to
coverage-<timestamp>.htmlin the workspace root using the Write tool. - Open via Bash:
open coverage-<timestamp>.html(macOS) orxdg-open(Linux). IfopenInBrowserMCP tool is available, use that instead. - Report: "Opened coverage heatmap — overall N% line coverage across M files. Saved to: "
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.
- 1mo ago First seen · 54 lines · 44 tokens per session scan A 87835372e96d
ide-coverage is a skill published in the GitHub repository Oolab-labs/patchwork-os (31 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 865 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to ide-coverage, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
verification-loop
A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.
cli-eval
Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with CI workflows from the CLI.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.