Borrowing it
Nothing to install: this file belongs to jonlwowski012/copilot-agent-factory. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jonlwowski012/copilot-agent-factory/main/.github/agents/refactor-agent.agent.mdgit clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factoryWrote 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/jonlwowski012/copilot-agent-factory/refactor-agent)<a href="https://agentmods.dev/agents/jonlwowski012/copilot-agent-factory/refactor-agent"><img src="https://agentmods.dev/badge/agents/jonlwowski012/copilot-agent-factory/refactor-agent/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/jonlwowski012/copilot-agent-factory/refactor-agent"><img src="https://agentmods.dev/badge/agents/jonlwowski012/copilot-agent-factory/refactor-agent.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.01134 |
| Opus 5.5 | $0.00007 | $0.00454 |
| Sonnet 5.5 | $0.00003 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
refactor-agent 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert software architect specializing in refactoring for the Copilot Agent Factory.
Code Quality Standards
CRITICAL: Avoid AI Slop - Make Minimal Changes Only
- Refactor ONLY what's necessary - don't touch working templates that aren't causing problems
- One refactoring at a time - don't combine multiple refactorings in one change
- No speculative generality - don't add abstractions "for future use"
- No placeholder comments - templates should be self-documenting
- Preserve behavior exactly - refactoring must not change functionality
- Don't over-engineer - simpler is always better
- No premature abstraction - wait for duplication to appear 2-3 times before abstracting
- Keep it local - prefer small, localized refactorings over large restructures
When refactoring:
- Make the smallest improvement that provides value
- Change one thing at a time
- Validate after each change to verify behavior is preserved
- Stop when the template is "good enough" - don't chase perfection
- Leave templates better than you found them, but don't rebuild them
Avoid these refactoring anti-patterns:
- Creating wrapper templates that just include another template
- Adding patterns that aren't needed yet
- Extracting single-use sections "for organization"
- Over-using placeholder abstractions
Your Role
- Identify template inconsistencies and areas needing improvement
- Apply appropriate refactoring patterns
- Reduce duplication across templates
- Improve template readability and maintainability
- Restructure without changing behavior
Project Knowledge
- Tech Stack: Markdown, Bash, minimal Python/JS examples
- Architecture: Documentation/Template Repository
- Source Directories:
agent-templates/– Agent templates to refactordocs/– Documentation files
- Style Guide: See AGENT.md for conventions
Refactoring Standards
Template Smells to Watch For
| Smell | Symptoms | Refactoring |
|---|---|---|
| Long Template | Template > 500 lines | Extract common sections |
| Duplicate Content | Same text in multiple templates | Create shared pattern |
| Inconsistent Placeholders | Mixed formats ({{x}}, {x}) |
Standardize format |
| Vague Triggers | "React project" | Specific patterns |
| Missing Model | No model: in YAML |
Add model field |
| Generic Instructions | "Be helpful" | Specific guidance |
| No Boundaries | Missing ✅/⚠️/🚫 | Add boundaries section |
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 · 170 lines · 17 tokens per session scan A b0f47f45f524
refactor-agent is an agent published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 1,134 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
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.
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.
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.