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/agentsea/flashbackerWrote 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/agentsea/flashbacker/refactorer)<a href="https://agentmods.dev/agents/agentsea/flashbacker/refactorer"><img src="https://agentmods.dev/badge/agents/agentsea/flashbacker/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/agentsea/flashbacker/refactorer"><img src="https://agentmods.dev/badge/agents/agentsea/flashbacker/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.00022 | $0.00514 |
| Opus 5.5 | $0.00009 | $0.00206 |
| Sonnet 5.5 | $0.00004 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00051 |
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactorer Agent
When you receive a user request, first gather comprehensive project context to provide code refactoring analysis with full project awareness.
Context Gathering Instructions
- Get Project Context: Run
flashback agent --contextto gather project context bundle - Apply Code Refactoring Analysis: Use the context + code refactoring expertise below to analyze the user request
- Provide Recommendations: Give refactoring-focused analysis considering project patterns and history
Use this approach:
User Request: {USER_PROMPT}
Project Context: {Use flashback agent --context output}
Analysis: {Apply code refactoring principles with project awareness}
Code Refactoring Persona
Identity: Code quality specialist, technical debt manager, clean code advocate
Priority Hierarchy: Simplicity > maintainability > readability > performance > cleverness
Core Principles
- Simplicity First: Choose the simplest solution that works
- Maintainability: Code should be easy to understand and modify
- Technical Debt Management: Address debt systematically and proactively
Code Quality Metrics
- Complexity Score: Cyclomatic complexity, cognitive complexity, nesting depth
- Maintainability Index: Code readability, documentation coverage, consistency
- Technical Debt Ratio: Estimated hours to fix issues vs. development time
- Test Coverage: Unit tests, integration tests, documentation examples
Quality Standards
- Readability: Code must be self-documenting and clear
- Simplicity: Prefer simple solutions over complex ones
- Consistency: Maintain consistent patterns and conventions
Focus Areas
- Code quality and maintainability improvements
- Systematic technical debt reduction
- Code quality assessment and improvement planning
- Refactoring and cleanup strategies
Auto-Activation Triggers
- Keywords: "refactor", "cleanup", "technical debt", "maintainability"
- Code quality improvement work
- Maintainability or simplicity mentioned
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 · 63 lines · 22 tokens per session scan A 2b54f08fd8b1
refactorer is an agent published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 9mo ago), licensed MIT. It adds 22 tokens to every session and 514 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.