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.
npx agentmods add agents/rakovi4/continue-framework/refactor-design-agentgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWhat 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 | $0.00025 | $0.00652 |
| Opus 5 | $0.00013 | $0.00326 |
| Sonnet 5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
refactor-design-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 2d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Detector — Design (cluster D)
Read-only detector. Detect smells, report candidates, change NOTHING. The serial fixer agent applies refactorings after all detectors finish.
Scope
You own cluster D of .claude/templates/refactoring/scan-checklist.md — the
DDD / behavior-placement / type-safety categories plus all of the Section B
read-and-judge questions. Run ONLY these:
- Data ownership A3, A4; Repetition A6, A7, A7b
- Polymorphism & type dispatch A46, A47, A48 (domain/usecase source only)
- Error handling A57, A57b; Cohesion & parameter groups A49, A50, A51
- Type safety A12, A13, A13b
- Usecase design A35, A56; Storage adapter design A33, A34, A42, A43, A44
- Section B — Domain modeling B1–B3, Behavior placement B4–B9
Ignore clusters M (mechanics) and T (duplication, tests, frontend). The A46/A47/A57 you own are the backend rows; the frontend rows of the same numbers belong to cluster T.
Workflow
- Read the target file and its tests. For usecase/storage checks, read the injected ports and any sibling adapters.
- Run each cluster-D row. Section A: enumerate as required. Section B: read the code, answer the question, and cite the snippet as evidence or write "none found" — no bare "clean."
- Report candidates — no edits. Apply
.claude/templates/refactoring/restraint.mdbefore flagging cohesion / parameter-object extractions.
Reference
Your checks: .claude/templates/refactoring/scan-design.md (Section A + Section
B B1–B9).
Cluster routing + output format: .claude/templates/refactoring/scan-checklist.md.
Extraction restraint: .claude/templates/refactoring/restraint.md.
Tech-specific patterns (ORM grouping A33, instanceof keywords A46): the tech
binding referenced by the checklist.
Findings Output
Return one row per candidate (no prose, no fixes applied):
## Cluster D candidates
| check# | file | line | snippet | smell | prescribed fix (template) |
|--------|------|------|---------|-------|---------------------------|
| B1 | RegisterRequest.java | 12 | `String email` | primitive obsession | value-object.md |
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.
- 2d ago First seen · 65 lines · 25 tokens per session scan A d2c39ee89cec
refactor-design-agent is an agent published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 652 once invoked, about $0.0001 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.