Borrowing it
Nothing to install: this file belongs to litoondev/claude-talk-to-figma-mcp-main. 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/litoondev/claude-talk-to-figma-mcp-main/main/CLAUDE.mdgit clone --depth 1 https://github.com/litoondev/claude-talk-to-figma-mcp-mainWrote 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/litoondev/claude-talk-to-figma-mcp-main/claude-md)<a href="https://agentmods.dev/instructions/litoondev/claude-talk-to-figma-mcp-main/claude-md"><img src="https://agentmods.dev/badge/instructions/litoondev/claude-talk-to-figma-mcp-main/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/litoondev/claude-talk-to-figma-mcp-main/claude-md"><img src="https://agentmods.dev/badge/instructions/litoondev/claude-talk-to-figma-mcp-main/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.01940 | $0.01940 |
| Opus 5 | $0.00970 | $0.00970 |
| Sonnet 5 | $0.00388 | $0.00388 |
| Haiku 4.5 | $0.00194 | $0.00194 |
Grade A, and why
claude-talk-to-figma-mcp-main 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 11d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Responsive Execution Rules
Scope, Variables, Hug Height & Layer Optimization.
Apply these rules to any work on an existing Figma design: responsive adjustments, layer cleanup, layer renaming, or related design-system tasks.
Core principle: Understand → Scope → Inspect Variables → Execute Only Requested Work → Fill Width → Hug Height → Optimize Relevant Layers → Validate → Stop.
1. Understand the designer request first
Identify exactly what was asked before touching anything. Never assume additional tasks.
| Request | Do only this |
|---|---|
| "Make the tablet responsive" | Tablet — 768px. Do not create or modify Mobile. |
| "Make the mobile responsive" | Mobile — 320px. Do not modify Tablet. |
| "Rename the layers" | Rename layers. No redesign, no spacing/typography changes, no new Auto Layout, no responsive versions, no unrelated cleanup. |
| "Optimize the layers" | Layer optimization only. |
Core scope rule: understand the request → define the scope → execute only that scope. No extra design work unless explicitly requested.
2. Breakpoints are processed separately
Standard breakpoints: Desktop 1440px · Tablet 768px · Mobile 320px. Only work on the breakpoint the designer requested.
-
Tablet-only: inspect the Desktop source → work only on the 768px frame → complete tablet responsiveness A to Z → validate → stop. Do not continue to Mobile.
-
Mobile-only: inspect the approved source → work only on the 320px frame → complete → validate → stop. Do not modify Tablet.
-
Tablet + Mobile: Phase 1 is Tablet, complete and fully checked (responsive, clean, correct variables, no fixed-height responsive content, structure optimized only where necessary). Then stop and ask:
Tablet responsiveness is complete. Should I proceed with the 320px Mobile version?
Only begin Mobile after confirmation.
Never process Tablet and Mobile simultaneously. Finish one breakpoint completely first.
3. Use existing Figma variables and tokens
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.
- 11d ago First seen · 189 lines · 1,940 tokens per session scan A b315799fd989
claude-talk-to-figma-mcp-main CLAUDE.md is an instructions file published in the GitHub repository litoondev/claude-talk-to-figma-mcp-main (0 stars, last pushed 4d ago), licensed MIT. It adds 1,940 tokens to every session, about $0.0097 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
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).
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.
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).