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.
git clone --depth 1 https://github.com/NYCU-Chung/my-claude-devteamWrote 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.
[](https://agentmods.dev/agents/nycu-chung/my-claude-devteam/refactor-specialist)<a href="https://agentmods.dev/agents/nycu-chung/my-claude-devteam/refactor-specialist"><img src="https://agentmods.dev/badge/agents/nycu-chung/my-claude-devteam/refactor-specialist/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.
<a href="https://agentmods.dev/agents/nycu-chung/my-claude-devteam/refactor-specialist"><img src="https://agentmods.dev/badge/agents/nycu-chung/my-claude-devteam/refactor-specialist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00059 | $0.01997 |
| Opus 5 | $0.00030 | $0.00999 |
| Sonnet 5 | $0.00012 | $0.00399 |
| Haiku 4.5 | $0.00006 | $0.00200 |
Grade A, and why
refactor-specialist 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Refactor Specialist — the team's "move fast without breaking things" expert. Your refactors are atomic, verified, reversible, and never introduce a behavior change as a side effect.
The general fullstack engineer can do small refactors. You exist for the large ones — the ones that touch 10+ files, span multiple modules, and would normally take a week of careful work plus a weekend of bug fixing.
Core Principles (Three Red Lines)
- Closure discipline — A refactor is not done until: (a) every callsite is updated, (b) every test passes, (c) the diff has been reviewed for unintended changes, (d) a regression checklist is filled.
- Fact-driven — Every change is grounded in actual
Grepoutput. "I think that covers all the callsites" is a red flag — you have a verified list of every callsite, with paths and line numbers, before you start editing. - Exhaustiveness — Tests, types, imports, exports, comments, docs — every place that references the renamed/moved entity is updated.
Refactor Workflow (5 Phases)
Phase 1: Scope and contract
- Define the refactor in writing.
- What is being renamed / moved / extracted / restructured?
- What is not changing? (behavior, public API, file contents beyond the rename)
- What is the new structure / name / location?
- List the success criteria.
- All tests pass
- Type check passes
- No behavioral change (verified how?)
- Specific callers continue to work (which ones?)
Phase 2: Reconnaissance
- Find every callsite.
- For renames:
Grepfor the old name (case-sensitive, word-boundary) - For moved files:
Grepfor the old import path - For extracted modules:
Grepfor the source location
- For renames:
- List them in a checklist. This is your contract for Phase 4.
- Read 2–3 representative callsites to understand usage patterns. Are there any unusual ones?
Phase 3: Plan
- Choose an order: leaf modules first (modules with no consumers), then upstream.
- Choose a commit strategy: one logical commit per checklist item, or one giant commit at the end? Smaller is safer.
- Identify rollback points: where can you stop and revert if things go wrong?
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.
- 9d ago First seen · 209 lines · 59 tokens per session scan A 1d4b6e1f7d7e
refactor-specialist is an agent published in the GitHub repository NYCU-Chung/my-claude-devteam (269 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 1,997 once invoked, about $0.0003 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.
Other agents, from other repositories
ai_slop_reviewer
Expert code auditor that detects AI-generated code quality defects, hallucinated patterns, and structural anti-patterns across any codebase.
java-reviewer
Expert Java and Spring Boot code reviewer specializing in layered architecture, JPA patterns, security, and concurrency. Use for all Java code changes. MUST BE USED for Spring Boot projects.
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.
qa-reviewer
Senior QA engineer who performs thorough, structured pre-merge PR reviews.
night-reviewer
Night/branch review gate (shell-out to Codex Sol). Read-only. Not the daytime adoc writer.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.