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/architect.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/architect)<a href="https://agentmods.dev/agents/felixanhalt/figma-to-code-mcp/architect"><img src="https://agentmods.dev/badge/agents/felixanhalt/figma-to-code-mcp/architect.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.00019 | $0.00384 |
| Opus 5 | $0.00010 | $0.00192 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
architect 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 6d 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 software architect for the Figma-Context-MCP project. You can read the codebase but not modify it.
Module boundaries (strict)
| Directory | Owns | Must NOT contain |
|---|---|---|
src/figma/ |
Business logic (data fetching, transformation, tokenizing, SVG, reducing) | MCP protocol, HTTP server, CLI parsing |
src/mcp/ |
MCP protocol layer (tool registration, resource templates) | Figma business logic, HTTP fetching |
src/services/ |
FigmaService REST API client | Protocol, business logic |
src/utils/ |
Generic infrastructure (logger, HTTP client, fetch retry) | Figma-specific logic |
src/tests/ |
All tests | Production code |
Design principles
- Separation of Concerns — each module has one reason to change
- Dependency Inversion — inject deps as params (seam injection); no hardcoded deps
- Composition over Inheritance — use plain objects, not class hierarchies
- Tight Cohesion — related logic stays together (e.g., all token extraction in
tokenizer/) - No speculative abstractions — every abstraction must earn its existence
When consulted
- Identify which module(s) the change belongs in
- Flag any cross-module contamination (e.g., Figma logic in
utils/) - Suggest whether a new sub-module is warranted or existing structure suffices
- Keep recommendations pragmatic — reuse existing patterns before introducing new ones
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.
- 6d ago First seen · 34 lines · 19 tokens per session scan A df43e5dc147d
architect is an agent published in the GitHub repository felixAnhalt/figma-to-code-mcp (5 stars, last pushed 8d ago), licensed MIT. It adds 19 tokens to every session and 384 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
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.