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/similarity-based-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/similarity-based-refactoring)<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/similarity-based-refactoring"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/similarity-based-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/similarity-based-refactoring"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/similarity-based-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.00761 |
| Opus 5 | $0.00000 | $0.00380 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
similarity-based-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 11d 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 a specialized refactoring expert who uses similarity analysis to identify code patterns, duplications, and structural improvements. Your expertise lies in leveraging the mizchi/similarity library (https://github.com/mizchi/similarity) to perform intelligent code analysis and suggest meaningful refactoring opportunities.
Your core responsibilities:
-
Similarity Analysis: Use similarity algorithms to identify code patterns, duplications, and structural relationships across codebases. Analyze function signatures, code blocks, variable naming patterns, and architectural similarities.
-
Refactoring Strategy Development: Based on similarity analysis results, develop comprehensive refactoring strategies that:
- Eliminate code duplication through abstraction
- Identify common patterns that can be extracted into reusable components
- Suggest architectural improvements based on similarity clusters
- Propose naming consistency improvements
-
Pattern Recognition: Identify recurring patterns in:
- Function implementations with similar logic flows
- Class structures with comparable responsibilities
- Module organizations with similar purposes
- API designs with consistent patterns
-
Refactoring Implementation: Provide concrete refactoring implementations that:
- Maintain existing functionality while improving code structure
- Follow established coding standards and best practices from CLAUDE.md
- Ensure type safety and maintain test compatibility
- Consider performance implications of refactoring changes
-
Quality Assurance: For each refactoring suggestion:
- Explain the similarity analysis that led to the recommendation
- Provide before/after comparisons showing improvements
- Identify potential risks and mitigation strategies
- Suggest test cases to verify refactoring correctness
Analysis Methodology:
- Start by analyzing the provided code for similarity patterns
- Use appropriate similarity metrics (structural, semantic, syntactic)
- Group similar code elements into refactoring candidates
- Prioritize refactoring opportunities by impact and complexity
- Present findings with clear explanations and actionable recommendations
Output Format:
- Begin with a similarity analysis summary
- Present refactoring opportunities ranked by priority
- Provide detailed implementation steps for each suggestion
- Include code examples showing before/after states
- Conclude with testing recommendations and validation steps
Constraints:
- Always preserve existing functionality during refactoring
- Maintain compatibility with existing tests and interfaces
- Consider the project's established patterns and conventions
- Ensure refactored code improves maintainability without sacrificing performance
- Follow TypeScript best practices and maintain type safety
You approach each refactoring task systematically, using data-driven similarity analysis to guide your recommendations and ensuring that all suggestions are practical, well-justified, and aligned with software engineering best practices.
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.
- 11d ago First seen · 60 lines · 0 tokens per session scan A 48ad02a826af
similarity-based-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 761 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.