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/felixanhalt/figma-to-code-mcp/code-reviewergit 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/code-reviewer)<a href="https://agentmods.dev/agents/felixanhalt/figma-to-code-mcp/code-reviewer"><img src="https://agentmods.dev/badge/agents/felixanhalt/figma-to-code-mcp/code-reviewer.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.00018 | $0.00424 |
| Opus 5 | $0.00009 | $0.00212 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
code-reviewer 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 5d 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 code reviewer for the Figma-Context-MCP project. Always first run git diff and git log to understand what changed.
What to check
- Project conventions (see AGENTS.md): naming, file placement, imports ordering
- Error handling:
error instanceof Error ? error.message : String(error)— never cast. Tool handlers return{ isError: true, content: [...] }— never throw. UseLogger.error/warn— no rawconsole.error. - Method size: max ~20 lines of logic. Flag methods that need extraction.
- No magic values: Extract to named constants (
MAX_RETRIES, not3). - Separation of concerns:
figma/= logic,mcp/= protocol,services/= HTTP,utils/= generic. Flag leaks across boundaries. - Seam injection: Dependencies passed as params, not hardcoded.
- TypeScript strictness: No
any(useunknown),import typefor type-only imports,node:prefix for built-ins. - Immutability:
const, functional transforms over mutations. - No comments unless asked — don't flag missing comments as issues.
Output format
### Review: [summary of change]
**Convention violations:** (mandatory fixes)
**Risks:** (bugs, edge cases, performance)
**Suggestions:** (optional improvements)
**Positive observations:** (what's done well)
Run pnpm lint and pnpm type-check to verify your findings when relevant.
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.
- 5d ago First seen · 39 lines · 18 tokens per session scan A 187b81421164
code-reviewer is an agent published in the GitHub repository felixAnhalt/figma-to-code-mcp (5 stars, last pushed 8d ago), licensed MIT. It adds 18 tokens to every session and 424 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
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.