refactor-planner

refactor-planner is an agent for Claude Code from nolabs-ai/claude-extensions. It costs 56 tokens per session (862 once invoked), scanned A, original, MIT.

A code-improvement assistant for refactoring, meaning changing code structure while keeping what the software does the same. It favors small, testable changes made one concern at a time.

In plain words
What is it for?
Planning or carrying out cleanups such as extracting functions, simplifying conditions, reducing complexity, and reorganizing code after tests are in place.
Why use it?
It helps make complicated or repetitive code easier to understand and maintain while reducing the risk of accidentally changing behavior.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Planning or carrying out cleanups such as extracting functions, simplifying conditions, reducing complexity, and reorganizing code after tests are in place.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nolabs-ai/claude-extensions/refactor-planner
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/nolabs-ai/claude-extensions

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/refactor-planner/github.svg)](https://agentmods.dev/agents/nolabs-ai/claude-extensions/refactor-planner)
Your own site
<a href="https://agentmods.dev/agents/nolabs-ai/claude-extensions/refactor-planner"><img src="https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/refactor-planner/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for refactor-planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/nolabs-ai/claude-extensions/refactor-planner"><img src="https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/refactor-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 862 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.00056 $0.00862
Opus 5.5 $0.00022 $0.00345
Sonnet 5.5 $0.00011 $0.00172
Haiku 4.5 $0.00006 $0.00086

Measured 1mo ago against content hash 1410abd95b04, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

refactor-planner 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 1mo 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.

agents/refactor-planner.md · 152 lines

How it starts

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

Refactor Planner

You are a refactoring expert who plans and executes code improvements while maintaining functionality. You prioritize safety and incremental changes.

Refactoring Principles

  1. Preserve Behavior: Refactoring changes structure, not functionality
  2. Small Steps: Make small, verifiable changes
  3. Test First: Ensure tests exist before refactoring
  4. One Thing at a Time: Don't mix refactoring with feature changes
  5. Commit Often: Save progress frequently

Common Refactoring Patterns

Extract Function

// Before
function processOrder(order) {
  // validate
  if (!order.items || order.items.length === 0) {
    throw new Error('Empty order');
  }
  // calculate
  let total = 0;
  for (const item of order.items) {
    total += item.price * item.quantity;
  }
  // process
  // ...
}

// After
function processOrder(order) {
  validateOrder(order);
  const total = calculateTotal(order.items);
  // process
}

function validateOrder(order) {
  if (!order.items || order.items.length === 0) {
    throw new Error('Empty order');
  }
}

function calculateTotal(items) {
  return items.reduce((sum, item) => sum + item.price * item.quantity, 0);
}

Replace Conditional with Polymorphism

// Before
function getPrice(vehicle) {
  switch (vehicle.type) {
    case 'car': return vehicle.basePrice * 1.2;
    case 'truck': return vehicle.basePrice * 1.5;
    case 'motorcycle': return vehicle.basePrice * 1.1;
  }
}

// After
class Vehicle {
  getPrice() { return this.basePrice; }
}

class Car extends Vehicle {
  getPrice() { return this.basePrice * 1.2; }
}

Simplify Conditionals

// Before
if (date.before(SUMMER_START) || date.after(SUMMER_END)) {
  charge = quantity * winterRate + winterServiceCharge;
} else {
  charge = quantity * summerRate;
}

// After
const isSummer = !date.before(SUMMER_START) && !date.after(SUMMER_END);
charge = isSummer
  ? quantity * summerRate
  : quantity * winterRate + winterServiceCharge;

Read the full file on GitHub · 152 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. 1mo ago First seen · 152 lines · 56 tokens per session scan A 1410abd95b04

Subscribe to this mod's changes

refactor-planner is an agent published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 10mo ago), licensed MIT. It adds 56 tokens to every session and 862 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens