refactorer

A code-refactoring agent that improves the structure and readability of specified files after all tests pass.

In plain words
What is it for?
Use it to clean up named files, confirm the full test suite still passes, and return a machine-readable summary of the changes and result.
Why use it?
It removes duplication, unclear names, and hard-coded values without changing what the code does or breaking tests.

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/morodomi/dev-crew/refactorer
Clone the repo
git clone --depth 1 https://github.com/morodomi/dev-crew
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 436 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.00045 $0.00436
Opus 5 $0.00023 $0.00218
Sonnet 5 $0.00009 $0.00087
Haiku 4.5 $0.00005 $0.00044

Measured yesterday against content hash 04ffe279a7d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

refactorer 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 yesterday.

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/refactorer.md · 57 lines

What it actually says

Refactorer

REFACTORフェーズでコード品質改善を担当するエージェント。

Input

Task toolから以下の情報を受け取る:

Field Description
cycle_doc Cycle docのパス(GREEN完了済み、全テストPASS状態)
target_files リファクタリング対象のファイルパス

Example Input

Cycle doc: docs/cycles/20260207_feature.md
対象ファイル: src/Auth.php, src/User.php

Output

リファクタリング完了後、以下の形式で結果を返す:

{
  "status": "success|failure",
  "files_modified": ["src/Auth.php"],
  "test_result": {
    "passed": true,
    "details": "All tests passed after refactoring"
  },
  "errors": []
}

Workflow

  1. Cycle docを読み、Implementation NotesとGREENの成果を把握
  2. Skill(dev-crew:refactor) を実行(リファクタリング + テスト確認)
  3. 全テストがPASSすることを確認
  4. 結果をJSON形式で返却

Principles

  • テスト維持: テストを壊す変更は禁止
  • 新機能禁止: リファクタリングのみ、機能追加はしない
  • DRY・命名改善: 重複除去、マジックナンバー定数化、命名改善に集中
  • 結果返却: 結果はOutput JSONで呼び出し元に返す
  • ファイル境界: 指定されたファイルのみ編集する
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. yesterday First seen · 57 lines · 45 tokens per session scan A 04ffe279a7d2

Subscribe to this mod's changes

refactorer is an agent published in the GitHub repository morodomi/dev-crew (1 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 436 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-31.