Borrowing it
Nothing to install: this file belongs to Oolab-labs/claude-ide-bridge. 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/claude-ide-bridge/main/.claude/skills/ide-coverage/SKILL.mdgit clone --depth 1 https://github.com/Oolab-labs/claude-ide-bridgeWrote 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/claude-ide-bridge/ide-coverage)<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-coverage"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/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/claude-ide-bridge/ide-coverage"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ide-coverage — 94% identical, 2 lines differ
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 20b7cb01dd22
ide-coverage is a skill published in the GitHub repository Oolab-labs/claude-ide-bridge (37 stars, last pushed 6mo ago), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-chaos
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…
verify-bb
Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after BB feature changes or when asked to verify or smoke-test BB. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected…
test-audit
Gate new or changed tests, and audit existing tests for low value, implementation coupling, duplication, and the test-only production seams they keep alive. Use when writing, changing, reviewing, or sweeping tests.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
maintain-verification-skill
Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift. Use for "maintain the verification skill", "audit the verify skill", or "refresh the verification feature map".