claude-ide-bridge: Skill for Claude Code

.claude/skills/ide-coverage/SKILL.md

ide-coverage is a skill for Claude Code from Oolab-labs/claude-ide-bridge. It costs 44 tokens per session (865 once invoked), scanned A, original, MIT.

A tool that turns test-coverage reports into a color-coded file-tree heatmap shown in a web browser. Test coverage measures which parts of the code were exercised by tests.

In plain words
What is it for?
Use it with LCOV or JSON coverage files to find reports, parse line coverage, and open a visual overview.
Why use it?
A coverage report can be difficult to scan as text; the heatmap makes files with more or less covered code easier to spot.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is Oolab-labs/claude-ide-bridge's own configuration. It tells Claude Code how to work on claude-ide-bridge itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-ide-bridge configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Oolab-labs/claude-ide-bridge/main/.claude/skills/ide-coverage/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Oolab-labs/claude-ide-bridge

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-coverage.svg)](https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-coverage)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 865 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.00044 $0.00865
Opus 5 $0.00022 $0.00432
Sonnet 5 $0.00009 $0.00173
Haiku 4.5 $0.00004 $0.00086

Measured 7d ago against content hash 20b7cb01dd22, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 7d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/ide-coverage/SKILL.md · 54 lines

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

  1. If $ARGUMENTS is a specific file path, use it directly.
  2. Otherwise use the Glob tool with patterns: **/lcov.info, **/coverage-summary.json, **/coverage-final.json (exclude node_modules).
  3. 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.
  4. If no coverage file found: report "No coverage data found. Run npm test -- --coverage (or equivalent) first." and stop.

Phase 2 — Parse coverage

  1. Use the Read tool to read the located coverage file.
  2. 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 s and statement map statementMap
  3. Build a list: { file: string (relative), pct: number, hitLines: number, totalLines: number }[]
  4. Group files by directory for the tree layout. Compute directory-level aggregate coverage.

Phase 3 — Generate and open HTML

  1. 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 CSS width: 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 — "
  2. Write the HTML to coverage-<timestamp>.html in the workspace root using the Write tool.
  3. Open via Bash: open coverage-<timestamp>.html (macOS) or xdg-open (Linux). If openInBrowser MCP tool is available, use that instead.
  4. Report: "Opened coverage heatmap — overall N% line coverage across M files. Saved to: "

Read the full file on GitHub · 54 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. 7d ago First seen · 54 lines · 44 tokens per session scan A 20b7cb01dd22

Subscribe to this mod's changes

ide-coverage is a skill published in the GitHub repository Oolab-labs/claude-ide-bridge (38 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 865 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-08-30.

Related

Other skills, from other repositories

lsp-refactor

End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests. Inlines lsp-impact + lsp-safe-edit + lsp-verify + lsp-test-correlation into one coordinated sequence.

blackwell-systems/agent-lsp · 57 tokens

lsp-test-correlation

Find and run the tests that cover a source file. Use after editing a file to discover exactly which test files and test functions need to run — without running the entire test suite.

blackwell-systems/agent-lsp · 42 tokens

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.

affaan-m/ECC · 49 tokens

cli-e2e

Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.

ComposioHQ/composio · 62 tokens

python-sdk

Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.

ComposioHQ/composio · 60 tokens

typescript-providers

Implement, modify, test, or document TypeScript provider packages under ts/packages/providers, including framework adapters for OpenAI, Anthropic, Google, LangChain, Mastra, Vercel, LlamaIndex, Cloudflare, and Claude Agent SDK. Use for provider-specific TS work; do not use for core-only changes.

ComposioHQ/composio · 70 tokens