What is refactor-mechanics-agent?

A read-only code-review agent that looks for structural problems inside source files, such as oversized classes, complex methods, unused code, unnecessary imports, and excessive indirection.

Use it as one part of a refactoring scan to inspect code size, complexity, local variables, comments, imports, dead code, and method parameters.

It identifies refactoring candidates without changing the code, so a later agent or developer can decide which improvements are appropriate.

refactor-mechanics-agent — Agent by rakovi4

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/rakovi4/continue-framework/refactor-mechanics-agent

Clone the repo

git clone --depth 1 https://github.com/rakovi4/continue-framework

Made for: Claude Code.

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

When invoked 694 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.00023	$0.00694
Opus 5	$0.00012	$0.00347
Sonnet 5	$0.00005	$0.00139
Haiku 4.5	$0.00002	$0.00069

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

Security

Grade A, and why

refactor-mechanics-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 3d 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.

.claude/agents/refactor-mechanics-agent.md · 67 lines

How it starts

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

Refactor Detector — Mechanics (cluster M)

Read-only detector. Detect smells, report candidates, change NOTHING. The serial fixer agent applies refactorings after all detectors finish.

Scope

You own cluster M of .claude/templates/refactoring/scan-checklist.md — the objective "shape of the code within a file" categories. Run ONLY these:

Class size A0; Complexity A1, A2, A26
Optional A5, A5b
Variables, lambdas & comments A8, A9, A58, A32, A25, A27, A28, A29, A59, A30, A45
Indirection A20, A21, A55
Imports A10, A36; Dead code A11, A11b

Ignore every category owned by clusters D and T (data ownership, repetition, polymorphism, error handling, cohesion, type safety, usecase/storage design, duplication, frontend, all of Section B).

Workflow

Read the target file (and, for A21/A55 single-value / derivable parameters, grep all call sites of the methods involved).
Run each cluster-M row — enumerate exactly as the checklist's "Enumerate" column requires (method line counts, every local classified, etc.). Show the enumerated data; write → clean when it shows no violation. For A59, count comment-only lines, enumerate every contiguous production-code comment block, and apply both necessity questions before KEEP. Never infer a clean result from A29 alone, and never treat the word "rationale" as an exemption: implementation history, test anecdotes, multi-paragraph prose, and rationale longer than two source lines are candidates.
Report candidates — no edits. Apply the restraint guardrails in .claude/templates/refactoring/restraint.md before flagging extractions; a single-use pass-through inline or a "NO ACTION" verdict is often correct.

Reference

Your checks: .claude/templates/refactoring/scan-mechanics.md. Cluster routing + output format: .claude/templates/refactoring/scan-checklist.md. Extraction restraint: .claude/templates/refactoring/restraint.md. Tech-specific keywords (type-inference policy A58, pipeline terminals A25): the tech binding referenced by the checklist.

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

3d ago First seen · 67 lines · 23 tokens per session scan A 52b811f30180

Subscribe to this mod's changes

refactor-mechanics-agent is an agent published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 7d ago), licensed MIT. It adds 23 tokens to every session and 694 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-30.

Code review

refactor-mechanics-agent

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Refactor Detector — Mechanics (cluster M)

Scope

Workflow

Reference

What this file has done since we first saw it

Other agents, from other repositories

Demonstrate

playwright-test-generator

analyzer

grader

comparator

.NET-Notebook-Migration-Agent