refactor

refactor is a command for Claude Code from Sagargupta16/claude-skills. It costs 11 tokens per session (169 once invoked), scanned A, original, MIT.

A command for finding code smells—such as long functions, repeated code, or deeply nested logic—and applying approved refactorings without changing behavior.

In plain words
What is it for?
Use it to inspect recent or selected files, review proposed improvements, apply them one at a time, run tests, and commit each change.
Why use it?
It reduces the risk of breaking working code by checking tests before and after each change. It also keeps unrelated code out of the cleanup.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the refactoring plugin — 1 skill, 1 command, 1 agent shipped together

Good fit Use it to inspect recent or selected files, review proposed improvements, apply them one at a time, run tests, and commit each change.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/sagargupta16/claude-skills/refactor
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.

Clone the repo
git clone --depth 1 https://github.com/Sagargupta16/claude-skills

Made for: Claude Code.

Or install refactoring, the plugin that ships this one along with the rest of its 1 skill, 1 command, 1 agent.

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 refactor

README.md
[![agentmods](https://agentmods.dev/badge/commands/sagargupta16/claude-skills/refactor.svg)](https://agentmods.dev/commands/sagargupta16/claude-skills/refactor)
Your own site
<a href="https://agentmods.dev/commands/sagargupta16/claude-skills/refactor"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-skills/refactor.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 169 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.00011 $0.00169
Opus 5 $0.00005 $0.00084
Sonnet 5 $0.00002 $0.00034
Haiku 4.5 $0.00001 $0.00017

Measured yesterday against content hash b4bc9442783d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

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

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.

plugins/refactoring/commands/refactor.md · 20 lines

What it actually says

Analyze code for refactoring opportunities and apply safe transformations.

Steps:

  1. Run tests to establish a passing baseline
  2. Identify the target: user-specified files or git diff --name-only for recent changes
  3. Read the target code and identify code smells (long functions, duplication, deep nesting, etc.)
  4. Present findings as a table: location, smell, suggested refactoring
  5. If user approves, apply refactorings one at a time:
    • Make one change
    • Run tests to verify no regression
    • Commit the change
  6. Never combine refactoring with behavior changes

Do NOT refactor code unrelated to the user's task. Present the plan before making changes.

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. yesterday Changed b4bc9442783d
  2. 7d ago First seen · 20 lines · 11 tokens per session scan A 490461c9746c

Subscribe to this mod's changes

refactor is a command published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 169 once invoked, about $0.0001 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-31.