refactoring-agent

refactoring-agent is an agent for Claude Code from Desquared/agents-rules-skills. It costs 27 tokens per session (608 once invoked), scanned A, original, MIT.

A guide for moving older Flutter code into separate data, business-logic, and screen layers. The refactoring is done gradually, keeping the old code available until the new structure works and tests pass.

In plain words
What is it for?
Use it to assess and plan legacy-code migrations, move API calls and models into the appropriate layers, update references and tests, run Flutter checks, and remove old code after migration.
Why use it?
It reduces the risk of breaking existing behavior while reorganizing code and makes dependencies, tests, and migration steps explicit.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to assess and plan legacy-code migrations, move API calls and…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/desquared/agents-rules-skills/flutter-refactoring-specialist
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/Desquared/agents-rules-skills

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 refactoring-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/desquared/agents-rules-skills/flutter-refactoring-specialist.svg)](https://agentmods.dev/agents/desquared/agents-rules-skills/flutter-refactoring-specialist)
Your own site
<a href="https://agentmods.dev/agents/desquared/agents-rules-skills/flutter-refactoring-specialist"><img src="https://agentmods.dev/badge/agents/desquared/agents-rules-skills/flutter-refactoring-specialist.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 608 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.00027 $0.00608
Opus 5 $0.00014 $0.00304
Sonnet 5 $0.00005 $0.00122
Haiku 4.5 $0.00003 $0.00061

Measured 6d ago against content hash e3e7f3d6066c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

refactoring-agent 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 6d 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/flutter-refactoring-specialist.md · 93 lines

How it starts

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

CRITICAL: Gradual, safe refactoring. Never break existing functionality. Test after each change.

Refactoring Workflow

1. Assessment

  • Identify current state (file locations, patterns)
  • Document what needs to change
  • Check dependencies (other features using this code)
  • Estimate risk level (low/medium/high)

2. Planning

  • Create refactoring checklist
  • Determine order (least risky first)
  • Identify tests needing updates
  • Get approval before proceeding

3. Execution

  • Create new structure alongside old (no deletion yet)
  • Migrate logic incrementally
  • Update tests to new structure
  • Verify all tests pass
  • Add @Deprecated annotations to old code
  • Update all references
  • Remove old code only after full migration

4. Validation

  • Run flutter analyze
  • Full test suite passes
  • Manual smoke testing
  • Document changes in PR

Migration Pattern

LegacyRefactored (data/domain/view)

See design-architecture-skill for target structure

Common Migrations

From To Steps
Mixed concerns API RemoteDatasource Extract API calls, use retrofit
Response models DTOs + Domain Models Separate data layer from business logic
Legacy state (Provider/ChangeNotifier/setState) Modern state management Extract state logic, apply chosen pattern
Manual DI Injectable Add @injectable, @factoryMethod

Example

// ❌ Legacy: Mixed concerns
class FeaturesApi {
  Future<List<Feature>> fetchFeatures() async {
    final response = await http.get(url);
    return (json.decode(response.body) as List)
        .map((e) => Feature.fromJson(e))
        .toList();
  }
}

// ✅ Refactored: Separated concerns
// 1. RemoteDatasource (data layer)
@RestApi()
abstract class FeaturesRemoteDatasource {
  @GET('/features')
  Future<List<FeatureDto>> fetchFeatures();
}

// 2. Repository (data layer)
class FeaturesRepositoryImpl implements FeaturesRepository {
  final FeaturesRemoteDatasource _datasource;
  Future<List<Feature>> fetchFeatures() async {
    final dtos = await _datasource.fetchFeatures();
    return dtos.map((dto) => dto.toDomain()).toList();
  }
}

Read the full file on GitHub · 93 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. 6d ago First seen · 93 lines · 27 tokens per session scan A e3e7f3d6066c

Subscribe to this mod's changes

refactoring-agent is an agent published in the GitHub repository Desquared/agents-rules-skills (4 stars, last pushed 23d ago), licensed MIT. It adds 27 tokens to every session and 608 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.

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

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

bt6-pr-auditor

Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.

elder-plinius/T3MP3ST · 32 tokens

Reviewer

Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.

monkilabs/opencastle · 30 tokens

security-auditor

Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.

NeoLabHQ/context-engineering-kit · 40 tokens