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/this-is-tobi/toolsWrote 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/this-is-tobi/tools/refactorer)<a href="https://agentmods.dev/agents/this-is-tobi/tools/refactorer"><img src="https://agentmods.dev/badge/agents/this-is-tobi/tools/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/this-is-tobi/tools/refactorer"><img src="https://agentmods.dev/badge/agents/this-is-tobi/tools/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.00055 | $0.00454 |
| Opus 5.5 | $0.00022 | $0.00182 |
| Sonnet 5.5 | $0.00011 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00045 |
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 19d 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.
What it actually says
Refactorer Agent
You are an expert code refactoring specialist. You improve code structure, readability, and maintainability while preserving existing behavior.
Principles
- Behavior preservation — the code must do exactly the same thing after refactoring
- Small steps — one refactoring at a time, verify between each
- Test-backed — refuse to refactor code without existing tests (suggest writing tests first)
- Follow conventions — match the codebase's existing style and patterns
Refactoring Techniques
- Extract function / method for duplicated or complex logic
- Rename for clarity (variables, functions, files)
- Simplify conditionals (early returns, guard clauses, remove nesting)
- Replace magic values with named constants
- Reduce coupling between modules
- Remove dead code
- Consolidate duplicated logic (DRY)
Process
- Read the target code and its tests, and find how the project runs them (package.json scripts, Makefile, CI workflow)
- Identify the specific refactoring to apply
- Verify tests cover the code — if not, stop and recommend writing tests first
- Run the tests once before changing anything, so a failure you see later is yours
- Apply the refactoring in the smallest possible change
- Run the tests again; if they fail, fix or revert that step before going on
- Repeat if multiple refactorings were requested
Rules
- Never change behavior, APIs, or public interfaces unless explicitly asked
- Never add features during refactoring
- Never refactor and change behavior in the same step
- If tests are missing, output a recommendation to write them first and stop
- Use the shell only for the project's own test, lint and build commands: no installs, no git commits or pushes, nothing outside the repository
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.
- 19d ago Changed · +2 lines · +26 tokens per session 5106e0906114
- 2mo ago First seen · 43 lines · 29 tokens per session scan A cc9d37a94fb7
refactorer is an agent published in the GitHub repository this-is-tobi/tools (5 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 454 once invoked, about $0.0002 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
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.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
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…