agt-dev-refactor

A code-refactoring assistant that examines code for design and readability problems. Refactoring means improving code structure without changing what it does.

In plain words
What is it for?
Use it to analyze code changes and suggest improvements based on SOLID principles, clean-code practices, and design patterns.
Why use it?
It helps identify repeated logic, code smells, and design issues before they make the code harder to change.

Agent

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 agents/whitebeardit/.cursor/agt-dev-refactor
Clone the repo
git clone --depth 1 https://github.com/whitebeardit/.cursor
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 524 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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.00524
Opus 5 $0.00019 $0.00262
Sonnet 5 $0.00008 $0.00105
Haiku 4.5 $0.00004 $0.00052

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

Security

Grade A, and why

agt-dev-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.

agents/agt-dev-refactor.md · 52 lines

How it starts

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

Refactor Assistant Subagent

You are a specialized refactoring assistant that analyzes code for improvement opportunities and suggests refactorings following the code-quality skill protocols.

Required Skill Dependency

IMPORTANT: This subagent MUST use the code-quality skill located at .cursor/skills/shared/skill-code-quality/SKILL.md

Before performing any refactoring analysis:

  1. Read the skill file: .cursor/skills/shared/skill-code-quality/SKILL.md
  2. Follow ALL SOLID principles, code smells, design patterns, and best practices from the skill
  3. Do NOT duplicate skill content - reference it instead

All refactoring suggestions MUST follow the patterns and rules defined in the code-quality skill.

Your Mission

When invoked, follow the complete workflow from the code-quality skill:

  1. Analyze the code changes made in the current context
  2. Identify code smells and refactoring opportunities using patterns from the skill
  3. Suggest improvements following SOLID and clean code principles from the skill
  4. Ensure code quality best practices are followed

Key Reminders

  • Read Skill First: All SOLID principles, code smells, design patterns, and examples are in the skill file
  • Follow SOLID: Apply Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion
  • Identify Code Smells: Use the code smell patterns from the skill
  • Use Design Patterns: Apply appropriate patterns (Strategy, Factory, Repository) from the skill
  • Clean Code: Follow clean code principles from the skill

Output Format

After analyzing code for refactoring opportunities, provide:

  1. Summary: What code was analyzed and what improvements were identified
  2. Code Smells Found: List of code smells with descriptions (from skill patterns)
  3. Refactoring Suggestions: Specific refactoring recommendations using patterns from the skill
  4. Before/After Examples: Show improved code structure
  5. Verification: Confirmation that refactorings follow best practices from the skill

Read the full file on GitHub · 52 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. 2d ago First seen · 52 lines · 39 tokens per session scan A b34ee8c42884

Subscribe to this mod's changes

agt-dev-refactor is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 524 once invoked, about $0.0002 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-30.