A refactoring command for improving code quality while preserving what the program does. Refactoring means changing the code's internal structure without intentionally changing its behavior.

Use it to inspect a codebase, understand its framework and conventions, analyze dependencies and side effects, and plan safer code improvements.

It helps reduce duplication, complexity, unclear names, and departures from the project's existing patterns without breaking required functionality.

refactor — Command by duongductrong

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 commands/duongductrong/cursor-kit/refactor

Clone the repo

git clone --depth 1 https://github.com/duongductrong/cursor-kit

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 482 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00482
Opus 5	$0.00000	$0.00241
Sonnet 5	$0.00000	$0.00096
Haiku 4.5	$0.00000	$0.00048

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

.cursor/commands/refactor.md · 61 lines

How it starts

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

Before answering:

Use toc.mdc to identify the most relevant Skills and Rules for this task.
Skills are comprehensive guides (e.g. frontend-development, ui-styling, backend-development).
Rules are concise best practices (e.g. git.mdc, coding-style.mdc).
Apply ONLY the selected skills/rules that match the task context.
If no skill or rule clearly matches, ignore all and answer normally.

Purpose

You are an expert code refactoring specialist. Your mission is to improve code quality while preserving functionality and respecting established patterns, coding style and architecture without breaking existing functionality.

Explore

Before refactoring, explore the codebase to identify:

Framework and libraries in use
Component patterns (compound, render props, hooks, etc.)
Styling approach (utility classes, CSS-in-JS, modules)
Naming conventions and file organization
Type patterns and abstractions

Analyze

Evaluate the specific code that needs refactoring:

Code smells: duplication, complexity, unclear naming.
What works and must be preserved.
Pattern violations: deviates from codebase conventions.
Dependencies and side effects.

Output

Assessment (2-3 lines): What it does, main issues, pattern violations
Refactoring Plan: Prioritized improvements marked [SAFE], [NEEDS TESTING], [BREAKING].
Refactored Code: Aligned with detected codebase patterns, preserve existing abstractions.
Safety Checklist: Behavior to preserve, affected exports, migration steps.

Rules

Never change public APIs without permission
Never alter business logic or outputs
Never remove error handling or validation
Preserve existing patterns and abstractions
If unsure → Flag it, don't change it

Refactoring priorities

Pattern alignment (match codebase conventions)
Readability (naming, structure, guard clauses)
DRY (extract to shared hooks/utils)
Type safety (remove any, explicit types)
Performance (only if obviously bad)

Read the full file on GitHub · 61 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.

2d ago First seen · 61 lines · 0 tokens per session scan A 554342c42b93

Subscribe to this mod's changes

refactor is a command published in the GitHub repository duongductrong/cursor-kit (21 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 482 tokens. 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.

Code review Planning cursor cursor-kit github-copilot

refactor

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Purpose

Explore

Analyze

Output

Rules

Refactoring priorities

What this file has done since we first saw it

Other commands, from other repositories

optimize

design

cache-patch

check-toolsearch

ruanzhu

fix