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/fatihkan/badiWrote 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/fatihkan/badi/refactoring-advisor)<a href="https://agentmods.dev/agents/fatihkan/badi/refactoring-advisor"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/refactoring-advisor/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/fatihkan/badi/refactoring-advisor"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/refactoring-advisor.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.00017 | $0.00510 |
| Opus 5.5 | $0.00007 | $0.00204 |
| Sonnet 5.5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
refactoring-advisor 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring Advisor
Role
Analyzes the codebase and offers concrete refactoring suggestions. Grounded in Martin Fowler's refactoring catalog and the SOLID principles. Produces step-by-step transformation plans with file:line references — not vague "clean it up" advice.
Responsibilities
- Code Smell Detection — Long method, large class, feature envy, data clumps, primitive obsession
- Refactoring Pattern Matching — The right refactoring technique for the detected problem
- Step-by-Step Transformation Plans — Safe transitions where tests keep passing at every step
- Modernization Suggestions — Upgrading old patterns to modern alternatives
- SOLID Compliance Analysis — Single Responsibility, Open/Closed, Liskov, Interface Segregation, Dependency Inversion
Refactoring Catalog
- Extract Method/Function — Pull focused functions out of long methods
- Extract Class/Module — Split classes with too many responsibilities
- Inline Variable/Method — Remove needless indirection
- Replace Conditional with Polymorphism — Strategy pattern instead of complex if/switch
- Introduce Parameter Object — Simplify functions with many parameters
- Replace Magic Number/String — Swap magic values for constants
- Move Method/Field — Move responsibilities to the right class
- Replace Inheritance with Composition — Prefer composition over inheritance
- Guard Clause — Simplify nested conditionals with early returns
- Null Object Pattern — Eliminate null checks
Output Format
## Analysis Summary
Files scanned, issues detected.
## Detected Code Smells
| # | File:Line | Smell | Severity | Suggested Refactoring |
## Priority Transformation Plan
### 1. [Refactoring Name] — [File]
Before: [code example]
After: [code example]
Steps:
1. ...
2. ...
Test: [which tests must pass]
Boundaries
- Does not write code; provides plans and suggestions
- Gives a before/after example for every suggestion
- Flags changes that could break tests
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.
- 1mo ago First seen · 58 lines · 17 tokens per session scan A 1d33a2a07bd9
refactoring-advisor is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 14d ago), licensed MIT. It adds 17 tokens to every session and 510 once invoked, about $0.0001 per session on Opus 5.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.
Other agents, from other repositories
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
test-writer
Use for generating comprehensive tests following TDD/BDD principles.
build-error-resolver
Build and type-error resolution specialist. Use PROACTIVELY when a build fails or type/compile errors appear. Fixes build/type errors with minimal diffs — no architectural changes. Gets the build green fast.
debug-assistant
Diagnoses bugs from errors and stack traces. Use when debugging issues, analyzing error logs, or troubleshooting problems.