Refactoring

Refactoring is a skill for Claude Code, Codex from tmcfarlane/oh-my-cursor. It costs 61 tokens per session (1,831 once invoked), scanned A, original, MIT.

A set of procedures for safely restructuring code, such as renaming functions, extracting methods, splitting classes, moving code, and modernising it. It includes checking references, dependencies, imports, tests, comments, and configuration.

In plain words
What is it for?
Use it for safe renames, method extraction, code migrations, complexity reduction, class splitting, and other changes that reorganise existing code.
Why use it?
It reduces the risk of breaking code when changing its internal structure. The checks help reveal usages and related files that are easy to miss during a manual edit.

Skill for Claude CodeCodex

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/tmcfarlane/oh-my-cursor/refactoring
Any agent
npx skills add tmcfarlane/oh-my-cursor --skill refactoring
Clone the repo
git clone --depth 1 https://github.com/tmcfarlane/oh-my-cursor

Made for: Claude Code, Codex.

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 Refactoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/tmcfarlane/oh-my-cursor/refactoring.svg)](https://agentmods.dev/skills/tmcfarlane/oh-my-cursor/refactoring)
Your own site
<a href="https://agentmods.dev/skills/tmcfarlane/oh-my-cursor/refactoring"><img src="https://agentmods.dev/badge/skills/tmcfarlane/oh-my-cursor/refactoring.svg" alt="Measured on agentmods" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,831 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00061 $0.01831
Opus 5 $0.00030 $0.00915
Sonnet 5 $0.00012 $0.00366
Haiku 4.5 $0.00006 $0.00183

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

Security

Grade A, and why

Refactoring scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

response = requests.get(f"/users/{user_id}")
skills/refactoring/SKILL.md · 351 lines

How it starts

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

Refactoring

Comprehensive refactoring skill for safe code restructuring, migrations, and modernization.

Core Capabilities

Safe Renaming

Rename identifiers across the codebase:

Rename workflow:

  1. Find all references: Search for all usages
  2. Identify scope: Module-local, package-wide, or public API
  3. Check dependencies: External code that might break
  4. Perform rename: Update all occurrences
  5. Verify: Run tests, check imports

Search patterns:

# Find all references to a function
grep -rn "function_name" --include="*.py"

# Find class usages
grep -rn "ClassName" --include="*.py"

# Find imports
grep -rn "from .* import.*function_name" --include="*.py"

Renaming considerations:

  • Update docstrings mentioning the old name
  • Update comments referencing the name
  • Update configuration files
  • Update tests
  • Consider deprecation period for public APIs

Method Extraction

Extract code into separate functions:

When to extract:

  • Code block is too long (> 20 lines)
  • Code is duplicated elsewhere
  • Code has a clear single purpose
  • Code can be tested independently

Extraction process:

  1. Identify the code block to extract
  2. Determine inputs (parameters)
  3. Determine outputs (return values)
  4. Create new function with clear name
  5. Replace original code with function call
  6. Add tests for new function

Before:

def process_order(order):
    # Validate order (candidate for extraction)
    if not order.items:
        raise ValueError("Empty order")
    if order.total < 0:
        raise ValueError("Invalid total")
    for item in order.items:
        if item.quantity <= 0:
            raise ValueError("Invalid quantity")

    # Process payment
    payment_result = gateway.charge(order.total)
    return payment_result

After:

def validate_order(order: Order) -> None:
    """Validate order has valid items and total."""
    if not order.items:
        raise ValueError("Empty order")
    if order.total < 0:
        raise ValueError("Invalid total")
    for item in order.items:
        if item.quantity <= 0:
            raise ValueError("Invalid quantity")

def process_order(order: Order) -> PaymentResult:
    validate_order(order)
    return gateway.charge(order.total)

Read the full file on GitHub · 351 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 · 351 lines · 61 tokens per session scan A 62d24be8a400

Subscribe to this mod's changes

Refactoring is a skill published in the GitHub repository tmcfarlane/oh-my-cursor (108 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 1,831 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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

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