agentmods.dev

ide-refactor

A refactoring process that uses IDE code intelligence, tests, and Git for rollback. Refactoring changes code structure without intending to change its behavior.

In plain words
What is it for?
Use it to rename symbols, apply code actions, run tests, and revert the refactor if the tests fail.
Why use it?
It protects against accidental breakage by checking the working tree first and testing the result before offering a rollback.

Skill for Claude CodeCodex

30 3d ago A scan 44 tokens original 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-refactor
Any agent
npx skills add Oolab-labs/patchwork-os --skill ide-refactor
Clone the repo
git clone --depth 1 https://github.com/Oolab-labs/patchwork-os

Made for: Claude Code, Codex.

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,138 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00044 $0.01138
Opus 5 $0.00022 $0.00569
Sonnet 5 $0.00009 $0.00228
Haiku 4.5 $0.00004 $0.00114

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

Security

Grade A, and why

ide-refactor 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 3d 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.

.claude/skills/ide-refactor/SKILL.md · 107 lines

How it starts

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

IDE Safe Refactor Workflow

Prerequisites

  1. Check if the getToolCapabilities MCP tool is available to you.

    • Not available (no MCP tool by that name): stop and tell the user: "This skill requires the Claude IDE Bridge with a connected VS Code extension. It uses LSP tools (rename symbol, code actions, references, snapshots) that have no CLI equivalent.

      To use this skill:

      1. Start the bridge: npm run start-all (in claude-ide-bridge/)
      2. Ensure the Claude IDE Bridge extension is installed in your IDE
      3. Use the claude --ide session (not remote-control)"

    • Available: call it. If extensionConnected is false: show the same message. If true: proceed.

Perform refactoring with a safety net. The safety net is git: the working tree is verified clean before anything is touched, so git checkout reverts the whole change if tests fail afterwards.

Workflow

Phase 1: Checkpoint

There is no snapshot tool. Git is the rollback mechanism, and it only works if the tree is clean first — otherwise a revert would discard the user's unrelated work along with the refactoring.

  1. Call getGitStatus.
    • Clean tree: proceed. git checkout -- . will revert everything this skill does.
    • Uncommitted changes present: stop and offer the choice — "You have uncommitted changes. I can't offer a clean rollback until they're saved. Commit them, or shall I gitStash them first and restore them after?" Never proceed silently: doing so leaves the user with no way to undo the refactor without also losing their own work.
  2. Confirm: "Working tree clean — git checkout will revert this. Starting refactoring: $ARGUMENTS"

Phase 2: Plan the refactoring

  1. Analyze what needs to change based on the description: $ARGUMENTS
  2. Use searchWorkspace and getDocumentSymbols to identify all affected symbols
  3. Use findReferences to map the impact across the codebase
  4. Use getCallHierarchy to understand dependency chains
  5. List all files that will be affected and confirm the plan

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

Subscribe to this mod's changes

ide-refactor is a skill published in the GitHub repository Oolab-labs/patchwork-os (30 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 1,138 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.

ai-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