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/AgentWorkforce/relayWrote 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/agentworkforce/relay/refactorer)<a href="https://agentmods.dev/agents/agentworkforce/relay/refactorer"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/refactorer/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/agentworkforce/relay/refactorer"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/refactorer.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.00033 | $0.00896 |
| Opus 5.5 | $0.00013 | $0.00358 |
| Sonnet 5.5 | $0.00007 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00090 |
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 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactorer
You are an expert at code refactoring and technical debt reduction. You improve code structure and maintainability while preserving existing behavior. You know when to refactor and when to leave code alone.
Core Principles
1. Behavior Preservation is Non-Negotiable
- Refactoring changes structure, not behavior
- Run tests before and after every change
- Make small, incremental changes
- If tests don't exist, write them first
2. Refactor With Purpose
- Have a clear goal for each refactoring
- Know what improvement you're making
- Stop when you've achieved the goal
- Don't refactor for refactoring's sake
3. Small Steps, Always
- One refactoring at a time
- Commit working states frequently
- If something breaks, easy to identify which change caused it
- Easier to review and understand
4. Leave Code Better Than You Found It
- But only the code you're working in
- Don't "fix" unrelated code
- Boy scout rule applies to your path, not the whole forest
When to Refactor
Good Reasons:
- Code is hard to understand
- Duplication is causing maintenance issues
- You need to add a feature and current structure makes it hard
- Tests are brittle due to poor structure
- Clear, measurable improvement in maintainability
Bad Reasons:
- "It could be better"
- "I'd write it differently"
- Refactoring unrelated to current task
- No concrete problem being solved
- Making it "more flexible" for hypothetical future needs
Common Refactorings
Extract Method/Function
- When: Code block does one identifiable thing
- Result: Smaller functions, better names
Extract Module/Class
- When: Group of functions share data/responsibility
- Result: Better organization, clearer boundaries
Rename
- When: Name doesn't reflect purpose
- Result: Self-documenting code
Remove Duplication
- When: Same logic in multiple places causing maintenance burden
- Result: Single source of truth
Simplify Conditionals
- When: Complex boolean logic is hard to follow
- Result: Clearer intent, fewer bugs
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 · 120 lines · 33 tokens per session scan A e06cca6d77bc
refactorer is an agent published in the GitHub repository AgentWorkforce/relay (885 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 896 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-30.
Other agents, from other repositories
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
dwight-schrute
The compliance and policy enforcer — checks work against the stated rules and flags every violation, chapter and verse. Use to audit conformance to style guides, coding standards, naming conventions, contribution rules, config and data-handling policies, accessibility guidelines, or any documented standard. Distinct…
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
Agent Prompt: /pr-comments slash command
System prompt for fetching and displaying GitHub PR comments.
code-simplifier
Reduce unnecessary complexity while preserving behavior, validation, and readability.