Borrowing it
Nothing to install: this file belongs to karthikyaddana/figma-mcp-free. 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/karthikyaddana/figma-mcp-free/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/karthikyaddana/figma-mcp-freeWrote 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/karthikyaddana/figma-mcp-free/copilot-instructions)<a href="https://agentmods.dev/instructions/karthikyaddana/figma-mcp-free/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/karthikyaddana/figma-mcp-free/copilot-instructions/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/karthikyaddana/figma-mcp-free/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/karthikyaddana/figma-mcp-free/copilot-instructions.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.00887 | $0.00887 |
| Opus 5 | $0.00443 | $0.00443 |
| Sonnet 5 | $0.00177 | $0.00177 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
figma-mcp-free copilot-instructions.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 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.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma MCP Free Rules
These rules define the recommended workflow when implementing Figma designs using the Figma MCP Free server.
Required Flow (do not skip)
- Run
get_design_contextfirst to fetch the structured representation for the exact node(s). - If the response is too large or truncated, run
get_metadatato get the high-level node map with layer IDs, names, types, positions, and sizes. Then re-fetch only the required node(s) withget_design_context. - Run
get_screenshotfor a visual reference of the node being implemented. - Run
get_variable_defsto retrieve design tokens (colors, spacing, typography variables). - Only after you have design context, screenshot, and token info, start implementation.
- Translate the output into this project's conventions, styles, and framework. Reuse existing color tokens, components, and typography.
- Validate against Figma for 1:1 look and behavior before marking complete.
Implementation Rules
- Treat the Figma MCP output as a representation of design structure and behavior, not as final code.
- Reuse existing components (buttons, inputs, typography, icon wrappers) instead of duplicating functionality.
- Use the project's color system, typography scale, and spacing tokens consistently.
- Respect existing routing, state management, and data-fetch patterns already adopted in the repo.
- Strive for 1:1 visual parity with the Figma design.
- Validate the final UI against the Figma screenshot for both look and behavior.
Tool Usage Guide
| Tool | When to Use |
|---|---|
get_metadata |
First, to understand structure of large designs. Returns lightweight node tree with IDs, types, positions, sizes. |
get_design_context |
Primary tool. Returns full layout, typography, fills, effects, components for selected nodes. |
get_screenshot |
Always. Provides visual reference for implementation validation. PNG preserves transparency. |
get_variable_defs |
To extract design tokens (colors, spacing, typography variables). |
get_styles |
To get all local text/paint/effect styles defined in the document. |
get_node |
To fetch a specific node by ID with full properties. |
get_selection |
To see what's currently selected in Figma. |
create_design_system_rules |
Once per project. Generates custom rules tailored to your stack. |
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 · 73 lines · 887 tokens per session scan A 148aa83ae4c1
figma-mcp-free copilot-instructions.md is an instructions file published in the GitHub repository karthikyaddana/figma-mcp-free (16 stars, last pushed 2mo ago), licensed MIT. It adds 887 tokens to every session, about $0.0044 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-30.
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).