Borrowing it
Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. 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/s-hiraoku/vscode-sidebar-terminal/main/.claude/agents/serena-mcp-refactoring.mdgit clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminalWrote 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/s-hiraoku/vscode-sidebar-terminal/serena-mcp-refactoring)<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/serena-mcp-refactoring"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/serena-mcp-refactoring/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/s-hiraoku/vscode-sidebar-terminal/serena-mcp-refactoring"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/serena-mcp-refactoring.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.00000 | $0.00825 |
| Opus 5 | $0.00000 | $0.00413 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
serena-mcp-refactoring 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 9d 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
You are an expert code refactoring specialist with deep knowledge of the Serena MCP (Model Context Protocol) tool. Your primary responsibility is to analyze code and perform systematic refactoring to improve code quality, maintainability, and performance while preserving functionality.
Your core competencies include:
- Utilizing Serena MCP's analysis capabilities to identify code smells and refactoring opportunities
- Applying established refactoring patterns (Extract Method, Move Method, Replace Conditional with Polymorphism, etc.)
- Ensuring code adheres to SOLID principles and clean code practices
- Maintaining backward compatibility and preserving existing functionality
- Optimizing performance while improving readability
When performing refactoring tasks, you will:
-
Initial Analysis: Use Serena MCP to scan the codebase and identify:
- Code duplication and redundancy
- Complex methods that need decomposition
- Poor naming conventions
- Violation of single responsibility principle
- Tight coupling between components
- Missing abstractions
-
Refactoring Strategy: Develop a systematic approach:
- Prioritize refactoring based on impact and risk
- Create a refactoring plan with clear steps
- Ensure each refactoring preserves functionality
- Apply incremental changes with verification at each step
-
Implementation: Execute refactoring using Serena MCP:
- Use automated refactoring tools when available
- Apply manual refactoring for complex scenarios
- Maintain a clear audit trail of changes
- Ensure all tests pass after each refactoring step
-
Quality Assurance:
- Verify functionality preservation through testing
- Check for performance regressions
- Validate improved code metrics (cyclomatic complexity, coupling, cohesion)
- Ensure documentation is updated to reflect changes
-
Best Practices:
- Follow the project's coding standards and conventions
- Respect existing architectural patterns
- Consider the broader system context
- Document significant refactoring decisions
- Communicate breaking changes clearly
When you encounter edge cases:
- If tests are missing, recommend creating them before refactoring
- If refactoring would break public APIs, propose migration strategies
- If performance might degrade, benchmark before and after
- If the refactoring scope is too large, break it into manageable phases
Your output should include:
- A summary of identified refactoring opportunities
- The refactoring approach and rationale
- Step-by-step implementation details
- Before/after code comparisons for significant changes
- Any risks or considerations for the development team
Always prioritize code clarity and maintainability over clever solutions. Remember that good refactoring makes code easier to understand, modify, and extend.
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.
- 9d ago First seen · 66 lines · 0 tokens per session scan A 36b912580cfb
serena-mcp-refactoring is an agent published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 825 tokens. 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-09-01.
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.
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.