agentmods.dev

claude-ide-bridge: Skill for Claude Code

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

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

A code-quality workflow that checks diagnostics, lint rules, formatting, imports, and tests across a project.

In plain words
What is it for?
It is for finding and fixing lint problems, organizing imports, formatting code, running tests, and optionally committing the cleanup.
Why use it?
It gathers routine cleanup tasks in one process and shows which issues remain after automatic fixes.

Skill for Claude Code

Written for Claude Code: disable-model-invocation 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 →

not rated 38repo 4mo ago A scan 40 tokens original MIT
View source ↗ Oolab-labs/claude-ide-bridge
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-quality/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-quality

README.md
[![agentmods](https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-quality/github.svg)](https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-quality)
Your own site
<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-quality"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-quality/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 ide-quality

Your own site · 80×15
<a href="https://agentmods.dev/skills/oolab-labs/claude-ide-bridge/ide-quality"><img src="https://agentmods.dev/badge/skills/oolab-labs/claude-ide-bridge/ide-quality.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,252 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.00040 $0.01252
Opus 5 $0.00020 $0.00626
Sonnet 5 $0.00008 $0.00250
Haiku 4.5 $0.00004 $0.00125

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

Security

Grade A, and why

ide-quality 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 9d 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-quality/SKILL.md · 128 lines

How it starts

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

IDE Quality Sweep Workflow

Prerequisites

  1. Check if the getToolCapabilities MCP tool is available to you.
    • Available: call it, check extensionConnected → use IDE Path below.
    • Not available: use CLI Path below.

IDE Path

Use this path when bridge MCP tools are available and extension is connected.

Phase 1: Assess the environment

  1. Use getToolCapabilities to discover available linters, formatters, and test runners
  2. Use getProjectInfo to understand the project type and languages
  3. Determine the scope: if $ARGUMENTS is provided, focus on that path; otherwise sweep the whole workspace

Phase 2: Collect all diagnostics

  1. Use getDiagnostics to get errors and warnings across the workspace
  2. Group diagnostics by severity (error → warning → info) and by file
  3. Report the total count: "Found N errors, M warnings across K files"

Phase 3: Auto-fix

  1. For each file with fixable diagnostics:
    • Use fixAllLintErrors to apply auto-fixes
    • Use organizeImports to clean up imports
    • Use formatDocument to apply consistent formatting
  2. Use getDiagnostics again to see what remains after auto-fixing
  3. Report: "Auto-fixed X issues. Y issues remain that need manual attention."

Phase 4: Manual fixes (remaining errors only)

  1. For remaining errors (not warnings), analyze the diagnostic message
  2. Use getHover and goToDefinition to understand the context
  3. Use editText to apply targeted fixes
  4. Use saveDocument after each fix

Phase 5: Verify

  1. Use runTests to run the test suite
  2. If tests fail, identify if the failure was caused by our changes:
    • Use getDiagnostics on test files
    • If we broke something, revert the specific change
  3. Use getDiagnostics one final time to confirm we haven't introduced new issues

Phase 6: Report and optionally commit

  1. Summarize all changes made:
    • Files modified
    • Issues fixed (auto vs manual)
    • Issues remaining (with explanations)
    • Test results
  2. Ask whether to commit the cleanup:
    • If yes: gitAdd the changed files, gitCommit with message "chore: fix lint errors and format code"

Read the full file on GitHub · 128 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. 9d ago First seen · 128 lines · 40 tokens per session scan A d832946a7fe1

Subscribe to this mod's changes

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

Claude CodeCode reviewaiclaudedeveloper-toolsidelsp
Related

Other skills, from other repositories

lsp-inspect

Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), comparison mode (--diff for branch-only issues), severity calibration by blast radius, fix suggestions, and confidence tiers. Applies a check taxonomy (dead symbols, silent failures, error wrapping…

blackwell-systems/agent-lsp · 126 tokens

lsp-dead-code

Enumerate exported symbols in a file and surface those with zero references across the workspace. Use when auditing for dead code, cleaning up APIs, or checking which exports are safe to remove.

blackwell-systems/agent-lsp · 43 tokens

lsp-impact

Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it. Use when refactoring, deleting, or changing the signature of any function, type, or method. Also accepts a file path to surface all exported-symbol impact in one shot.

blackwell-systems/agent-lsp · 67 tokens

lsp-concurrency-audit

Concurrency safety audit for a type or file. Maps all fields, traces which are accessed from concurrent contexts (goroutines, threads, async tasks), and flags fields that lack synchronization. Produces a field-level safety report. Language-agnostic across 4 concurrency families.

blackwell-systems/agent-lsp · 61 tokens

go-testing

Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.

Gentleman-Programming/gentle-ai · 26 tokens

security-review

Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging.…

waybarrios/opencode-power-pack · 64 tokens