Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/silships/figma-cli/claude-mdgit clone --depth 1 https://github.com/silships/figma-cliWhat 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 | $0.10854 | $0.10854 |
| Opus 5 | $0.05427 | $0.05427 |
| Sonnet 5 | $0.02171 | $0.02171 |
| Haiku 4.5 | $0.01085 | $0.01085 |
Grade A, and why
figma-cli 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 3d 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 — 758 lines — stays where its author put it; the contents beside it link to each section on GitHub.
figma-ds-cli
CLI that controls Figma Desktop directly. No API key needed.
Quick Reference
| User says | Command |
|---|---|
| "connect to figma" | figma-cli connect |
| "add shadcn colors" | figma-cli tokens preset shadcn |
| "add tailwind colors" | figma-cli tokens tailwind |
| "show colors on canvas" | figma-cli var visualize |
| "create dashboard" | figma-cli blocks create dashboard-01 |
| "list blocks" | figma-cli blocks list |
| "create cards/buttons" | render-batch + node to-component |
| "create a rectangle/frame" | figma-cli render '<Frame>...' |
| "convert to component" | figma-cli node to-component "ID" |
| "use the existing X component" / "don't rebuild, instance it" | figma-cli instantiate "X" |
| "what component already exists for X" | figma-cli spec X (shows the reuse handle) |
| "list variables" | figma-cli var list |
| "find nodes named X" | figma-cli find "X" |
| "what's on canvas" | figma-cli canvas info |
| "export as PNG/SVG" | figma-cli export png |
| "extract gradient from image" / "rebuild this gradient" | figma-cli gradient extract <image> |
| "apply image gradient to a frame" | figma-cli gradient extract <image> --apply-to <nodeId> |
| "match this mesh / blossom / aurora background" | figma-cli gradient extract <image> --mode mesh --apply-to <frameId> |
| "create a wallpaper / mesh gradient from these colors" | figma-cli gradient mesh "#a,#b,#c" --size 1920x1080 |
| "export the design system as markdown" / "create a DESIGN.md" | figma-cli extract |
| "make the design system testable" / "lock this in" / "contract" | figma-cli snapshot (writes design.json, commit it) |
| "did anything change / drift?" / "verify the file" / "check in CI" | figma-cli check |
| "write rules for our components" / "validate the components" | figma-cli rules gen then figma-cli check |
| "prove the tokens survive a roundtrip" / "why did tokens import white" | figma-cli check --roundtrip |
| "export only the tokens" | figma-cli extract --sections tokens |
| "extract/document the X page" | figma-cli extract --pages "X" |
| "extract what I selected" | figma-cli extract --selection |
| "import my tailwind colors" | figma-cli import tailwind.config.js |
| "import our css variables" | figma-cli import src/globals.css |
| "import design tokens json" | figma-cli import tokens.json |
| "export tokens as DTCG / design tokens json" | figma-cli export dtcg tokens.json |
| "export tokens as CSS / Tailwind" | figma-cli export css / figma-cli export tailwind |
| "load our storybook" | figma-cli import http://localhost:6006 |
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.
- 3d ago First seen · 758 lines · 10,854 tokens per session scan A 30a312f2911c
figma-cli CLAUDE.md is an instructions file published in the GitHub repository silships/figma-cli (919 stars, last pushed 21d ago), licensed MIT. It adds 10,854 tokens to every session, about $0.0543 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.