Borrowing it
Nothing to install: this file belongs to felixAnhalt/figma-to-code-mcp. 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/felixAnhalt/figma-to-code-mcp/main/.opencode/agents/refactorer.mdgit clone --depth 1 https://github.com/felixAnhalt/figma-to-code-mcpWrote 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/felixanhalt/figma-to-code-mcp/refactorer)<a href="https://agentmods.dev/agents/felixanhalt/figma-to-code-mcp/refactorer"><img src="https://agentmods.dev/badge/agents/felixanhalt/figma-to-code-mcp/refactorer.svg" alt="Measured on agentmods" 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.00020 | $0.00558 |
| Opus 5 | $0.00010 | $0.00279 |
| Sonnet 5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
refactorer 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 8d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a codebase scout. Your job is to find structural problems and report them as a prioritized list of refactoring opportunities. You do NOT execute refactors — you discover and describe.
How to scout
-
Read AGENTS.md first — understand the project's conventions, module boundaries, naming rules, and architectural principles. These are your evaluation criteria.
-
Scan for these categories of issues:
Separation of Concerns
- API calls living outside the designated service/data-access layer
- Business logic leaking into utility/infrastructure modules
- Protocol/transport concerns mixed with domain logic
- Look at imports — if module A imports from module B and the conventions say they should be separated, flag it
Duplication & dead weight
- Near-duplicate functions with similar URL construction, header setup, or data shaping
- Dead files/functions that were superseded but never removed
- Functions that are only called from one place and could be inlined
Method sizing
- Functions exceeding ~20 lines of logic (not counting formatting, verbose setup, or multiline strings)
- Files with too many responsibilities (flag when a single file combines data fetching, transformation, and output formatting)
Magic values
- Raw strings/numbers used inline where a named constant would be clearer
- Repeated literals across files that should be a single source of truth
Type safety
as anycasts — suggestunknownwith narrowing instead- Objects that could benefit from
as const - Type-only imports using regular
import
Public API surface
- Exports that don't need to be public (only used internally)
- Re-exports of functions that violate layering (e.g., the public API re-exporting internal bypass functions)
Report format
## Refactoring Opportunities
### [Priority: High] Category — Short title
**Location:** file:line(s)
**Problem:** concise description
**Suggestion:** what should change
**Risk:** low/medium/high — how likely this breaks things
### [Priority: Medium] ...
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.
- 8d ago First seen · 74 lines · 20 tokens per session scan A f3062f67bb62
refactorer is an agent published in the GitHub repository felixAnhalt/figma-to-code-mcp (5 stars, last pushed 11d ago), licensed MIT. It adds 20 tokens to every session and 558 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-31.
Other agents, from other repositories
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.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.