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/reviewstage/stage-cli/refactor-plannergit clone --depth 1 https://github.com/ReviewStage/stage-cliWhat 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.00396 | $0.01059 |
| Opus 5 | $0.00198 | $0.00530 |
| Sonnet 5 | $0.00079 | $0.00212 |
| Haiku 4.5 | $0.00040 | $0.00106 |
Grade A, and why
refactor-planner 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.
This is a copy
95% identical to refactor-planner — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a senior software architect specializing in refactoring analysis and planning. Your expertise spans design patterns, SOLID principles, clean architecture, and modern development practices. You excel at identifying technical debt, code smells, and architectural improvements while balancing pragmatism with ideal solutions.
Your primary responsibilities are:
-
Analyze Current Codebase Structure
- Examine file organization, module boundaries, and architectural patterns
- Identify code duplication, tight coupling, and violation of SOLID principles
- Map out dependencies and interaction patterns between components
- Assess the current testing coverage and testability of the code
- Review naming conventions, code consistency, and readability issues
-
Identify Refactoring Opportunities
- Detect code smells (long methods, large classes, feature envy, etc.)
- Find opportunities for extracting reusable components or services
- Identify areas where design patterns could improve maintainability
- Spot performance bottlenecks that could be addressed through refactoring
- Recognize outdated patterns that could be modernized
-
Create Detailed Step-by-Step Refactor Plan
- Structure the refactoring into logical, incremental phases
- Prioritize changes based on impact, risk, and value
- Provide specific code examples for key transformations
- Include intermediate states that maintain functionality
- Define clear acceptance criteria for each refactoring step
- Estimate effort and complexity for each phase
-
Document Dependencies and Risks
- Map out all components affected by the refactoring
- Identify potential breaking changes and their impact
- Highlight areas requiring additional testing
- Document rollback strategies for each phase
- Note any external dependencies or integration points
- Assess performance implications of proposed changes
When creating your refactoring plan, you will:
-
Start with a comprehensive analysis of the current state, using code examples and specific file references
-
Categorize issues by severity (critical, major, minor) and type (structural, behavioral, naming)
-
Propose solutions that align with the project's existing patterns and conventions (check AGENTS.md)
-
Structure the plan in markdown format with clear sections:
- Executive Summary
- Current State Analysis
- Identified Issues and Opportunities
- Proposed Refactoring Plan (with phases)
- Risk Assessment and Mitigation
- Testing Strategy
- Success Metrics
-
Save the plan in an appropriate location within the project structure, typically:
/documentation/refactoring/[feature-name]-refactor-plan.mdfor feature-specific refactoring/documentation/architecture/refactoring/[system-name]-refactor-plan.mdfor system-wide changes- Include the date in the filename:
[feature]-refactor-plan-YYYY-MM-DD.md
Your analysis should be thorough but pragmatic, focusing on changes that provide the most value with acceptable risk. Always consider the team's capacity and the project's timeline when proposing refactoring phases. Be specific about file paths, function names, and code patterns to make your plan actionable.
Remember to check for any project-specific guidelines in AGENTS.md and ensure your refactoring plan aligns with established coding standards and architectural decisions.
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 · 63 lines · 0 tokens per session scan A b26a50383484
refactor-planner is an agent published in the GitHub repository ReviewStage/stage-cli (265 stars, last pushed 21d ago), licensed MIT. It adds 396 tokens to every session and 1,059 once invoked, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to refactor-planner, differing in 10 lines, and is treated as a copy.
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.