Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/echobt/figma-mcp/claude-md)<a href="https://agentmods.dev/instructions/echobt/figma-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/echobt/figma-mcp/claude-md.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.03573 | $0.03573 |
| Opus 5 | $0.01786 | $0.01786 |
| Sonnet 5 | $0.00715 | $0.00715 |
| Haiku 4.5 | $0.00357 | $0.00357 |
Grade A, and why
figma-mcp CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fig MCP Server
Project Overview
An MCP (Model Context Protocol) server for parsing .fig files. This enables AI assistants to understand and extract design information from the .fig file format for implementation guidance.
Architecture
Core Components
-
Parser (
src/parser/)fig-reader.ts- ZIP archive extraction using Central Directory (handles data descriptors)kiwi-parser.ts- Binary kiwi format parsing with deflate + zstd decompressionlayout-inference.ts- Converts raw node data to structured layout informationtypes.ts- TypeScript type definitions for.figdocument structure
-
MCP Server (
src/mcp/)server.ts- MCP server implementation with tools for querying fig files
-
Utilities
inspect-fig.ts- CLI tool for inspecting fig files during developmenttest-parser.ts- Local tool-flow test harness for image tools
-
Renderer (
src/renderer/)render-screen.ts- Main SVG renderer for node subtreesrender-types.ts- TypeScript types for renderingrender-utils.ts- Transform, path building, and XML utilitiespaint-utils.ts- Paint/fill/stroke handlingvector-renderer.ts- Vector path decoding and renderingscreenshot.ts- SVG to PNG conversion via resvgindex.ts- Public exports for the renderer module
-
Web Viewer (
src/web-viewer/)server.ts- HTTP server wrapping existing parser/rendererbuild-client.ts- esbuild bundler for client codeclient/- Browser-based UI (index.html, styles.css, viewer.ts)
File Format Details
.fig Archive Structure
.fig files are ZIP archives. Important: They use data descriptors (flag bit 3), so sizes must be read from Central Directory, not local headers.
Contents:
canvas.fig- Main document data (kiwi binary format, compressed)meta.json- File metadata (name, background color, etc.)thumbnail.png- Preview imageimages/- Image assets (hash-named files)videos/- Video assets (if any)
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 · 354 lines · 3,573 tokens per session scan A 15af13b0bf56
figma-mcp CLAUDE.md is an instructions file published in the GitHub repository echobt/figma-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 3,573 tokens to every session, about $0.0179 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 instructions, from other repositories
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).
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 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).
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.