Borrowing it
Nothing to install: this file belongs to sso-ss/figma-unified-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/sso-ss/figma-unified-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/sso-ss/figma-unified-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/instructions/sso-ss/figma-unified-mcp/claude-md)<a href="https://agentmods.dev/instructions/sso-ss/figma-unified-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/sso-ss/figma-unified-mcp/claude-md/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/instructions/sso-ss/figma-unified-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/sso-ss/figma-unified-mcp/claude-md.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.02662 | $0.02662 |
| Opus 5 | $0.01331 | $0.01331 |
| Sonnet 5 | $0.00532 | $0.00532 |
| Haiku 4.5 | $0.00266 | $0.00266 |
Grade A, and why
figma-unified-mcp CLAUDE.md scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Never** fetch Figma data via raw `curl` commands or manually generate code when a dedicated tool exists. How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions — figma-unified-mcp
CRITICAL: Always Check Available Tools & Agent Skills First
Before executing ANY user request related to Figma, you MUST:
- List your available MCP tools — check if a
figma_*tool already handles the task - List your available agent skills — check if a skill already orchestrates the workflow
- Use the existing tool/skill — do NOT manually replicate what a tool already does
Never fetch Figma data via raw curl commands or manually generate code when a dedicated tool exists.
Available Tools (106)
Connection (3)
figma_status, figma_connect_plugin, figma_send_command
Utility (3)
figma_cache (inspect/clear in-memory library cache), figma_run (escape hatch for non-full profiles), figma_skill (run a registered agent skill by name)
Read (32 — via REST API + Plugin Bridge)
figma_get_file, figma_get_node, figma_get_nodes, figma_get_styles (fileKey=REST, none=plugin local), figma_get_components (source: file/local/library), figma_get_variables, figma_get_comments, figma_post_comment, figma_search, figma_get_selection, figma_get_team_components, figma_get_team_styles, figma_get_component, figma_get_style, figma_get_library_items_used, figma_get_file_versions, figma_get_team_projects, figma_get_project_files, figma_scan_text_nodes, figma_scan_nodes_by_types, figma_set_focus, figma_set_selections, figma_get_library_collections, figma_get_library_variables, figma_get_viewport, figma_import_component_by_key, figma_import_style_by_key, figma_get_code_connect_map, figma_get_design_system_rules, figma_export_png, figma_create_page, figma_switch_page
Create (10 — via Plugin Bridge)
figma_create_frame, figma_create_rectangle, figma_create_ellipse, figma_create_text, figma_create_component, figma_create_instance, figma_create_line, figma_create_path, figma_create_from_svg, figma_batch
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.
- 12d ago First seen · 160 lines · 2,662 tokens per session scan A b403fe017b01
figma-unified-mcp CLAUDE.md is an instructions file published in the GitHub repository sso-ss/figma-unified-mcp (4 stars, last pushed 6mo ago), licensed MIT. It adds 2,662 tokens to every session, about $0.0133 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).