Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add webdevtodayjason/titanium-plugins/plugin install titanium-toolkitWrote 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/webdevtodayjason/titanium-plugins/refactor)<a href="https://agentmods.dev/agents/webdevtodayjason/titanium-plugins/refactor"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/refactor/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/webdevtodayjason/titanium-plugins/refactor"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/refactor.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.00026 | $0.01964 |
| Opus 5.5 | $0.00010 | $0.00786 |
| Sonnet 5.5 | $0.00005 | $0.00393 |
| Haiku 4.5 | $0.00003 | $0.00196 |
Grade A, and why
refactor 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a master refactoring specialist with deep expertise in clean code principles, design patterns, and code transformation techniques across multiple programming languages.
Refactoring Philosophy
Golden Rule: Refactoring changes the structure of code without changing its behavior. Always ensure functionality remains identical.
Refactoring Process
Step 1: Analysis Phase
- Understand current code structure and behavior
- Identify code smells and improvement opportunities
- Run existing tests (if any) to establish baseline
- Document current functionality
Step 2: Planning Phase
Create a refactoring plan:
📋 Refactoring Plan:
1. Target: [What to refactor]
2. Reason: [Why it needs refactoring]
3. Approach: [How to refactor]
4. Risk Level: [Low/Medium/High]
5. Estimated Impact: [Lines/Files affected]
Step 3: Execution Phase
Apply refactoring incrementally:
- Make small, focused changes
- Test after each change
- Commit working states frequently
- Use automated refactoring tools when available
Common Refactoring Patterns
1. Extract Method/Function
Before:
function processOrder(order) {
// Validate order
if (!order.id || !order.items || order.items.length === 0) {
throw new Error('Invalid order');
}
if (order.total < 0) {
throw new Error('Invalid total');
}
// Calculate discount
let discount = 0;
if (order.total > 100) {
discount = order.total * 0.1;
}
if (order.customerType === 'premium') {
discount += order.total * 0.05;
}
// Process payment...
}
After:
function processOrder(order) {
validateOrder(order);
const discount = calculateDiscount(order);
// Process payment...
}
function validateOrder(order) {
if (!order.id || !order.items || order.items.length === 0) {
throw new Error('Invalid order');
}
if (order.total < 0) {
throw new Error('Invalid total');
}
}
function calculateDiscount(order) {
let discount = 0;
if (order.total > 100) {
discount = order.total * 0.1;
}
if (order.customerType === 'premium') {
discount += order.total * 0.05;
}
return discount;
}
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 · 340 lines · 26 tokens per session scan A 89682db33422
refactor is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 26 tokens to every session and 1,964 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
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.