agentmods.dev

ide-quality

A workflow for checking code quality across multiple programming languages with either connected editor tools or command-line tools. It collects diagnostics, applies available fixes, organises imports, formats files, and runs tests.

In plain words
What is it for?
Use it to inspect a project, find errors and warnings, fix lint issues, organise imports, format code, run tests, and optionally commit the cleanup.
Why use it?
It gathers common cleanup and verification work into one repeatable review, so errors and warnings are easier to find before changes are shared.

Skill for Claude CodeCodex

30 2d ago A scan 40 tokens copy · 100% MIT
View the source file Oolab-labs/patchwork-os
Install

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.

agentmods
npx agentmods add skills/oolab-labs/patchwork-os/ide-quality
Any agent
npx skills add Oolab-labs/patchwork-os --skill ide-quality
Clone the repo
git clone --depth 1 https://github.com/Oolab-labs/patchwork-os

Made for: Claude Code, Codex.

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. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00040 $0.01252
Opus 5 $0.00020 $0.00626
Sonnet 5 $0.00008 $0.00250
Haiku 4.5 $0.00004 $0.00125

Measured 2d ago against content hash d832946a7fe1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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

This is a copy

100% identical to ide-quality — 0 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.

.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. 2d 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/patchwork-os (30 stars, last pushed 2d 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. It is 100% identical to ide-quality, differing in 0 lines, and is treated as a copy.

Debuggingai-agentanthropicapproval-queueautomationclaudeclaude-code
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens