Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/PracticalSwan/agent-skillsnpx agentmods add skills/practicalswan/agent-skills/figma-useWrote 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/skills/practicalswan/agent-skills/figma-use)<a href="https://agentmods.dev/skills/practicalswan/agent-skills/figma-use"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/figma-use/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/skills/practicalswan/agent-skills/figma-use"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/figma-use.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.00114 | $0.08741 |
| Opus 5.5 | $0.00046 | $0.03496 |
| Sonnet 5.5 | $0.00023 | $0.01748 |
| Haiku 4.5 | $0.00011 | $0.00874 |
Grade A, and why
figma-use 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.
This is a copy
86% identical to figma-use — 194 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
use_figma — Figma Plugin API Skill
Use the use_figma tool to execute JavaScript in Figma files via the Plugin API. All detailed reference docs live in references/.
Always include figma-use in the comma-separated skillNames parameter when calling use_figma. If this skill was loaded via an MCP resource, you MUST prefix the name with resource: (e.g. resource:figma-use). This is a logging parameter used to track skill usage — it does not affect execution.
If Figma MCP tools appear as deferred tools, batch-load all their schemas in a single ToolSearch call using the select: syntax — e.g. ToolSearch query="select:use_figma,get_screenshot,get_metadata,create_new_file". One round trip beats six.
MANDATORY for visible design changes: Before the first mutating use_figma call, load figma-generate-design alongside this skill and include both names in every mutating call’s skillNames. This applies from a single visible property or element to a full page, screen, or composed multi-section view—even when the user calls that view a component. figma-use provides the Plugin API rules; figma-generate-design provides design-system discovery through search_design_system, asset importing, and incremental assembly.
Reusable library exception: If the primary deliverable is a reusable component, component set, variant system, variable/token collection, style foundation, or other library asset intended for reuse or publication, load figma-generate-library instead. It provides the component-creation workflow—variable foundations, variant sets, and design-token bindings—that figma-use alone does not cover. For tasks that include both library assets and a composed design that uses them, load both companion skills. Read-only use_figma calls need neither.
Before anything, load plugin-api-standalone.index.md to understand what is possible. When you are asked to write plugin API code, use this context to grep plugin-api-standalone.d.ts for relevant types, methods, and properties. This is the definitive source of truth for the API surface. It is a large typings file, so do not load it all at once, grep for relevant sections as needed.
IMPORTANT: Whenever you work with design systems, start with working-with-design-systems/wwds.md to understand the key concepts, processes, and guidelines for working with design systems in Figma. Then load the more specific references for components, variables, text styles, and effect styles as needed.
What ships with it
21 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- CHANGELOG.md 4.0 KB
- references/api-reference.md 16 KB
- references/common-patterns.md 14 KB
- references/component-patterns.md 24 KB
- references/effect-style-patterns.md 3.1 KB
- references/gotchas.md 52 KB
- references/plugin-api-patterns.md 16 KB
- references/plugin-api-standalone.d.ts 394 KB runs code
- references/plugin-api-standalone.index.md 34 KB
- references/text-style-patterns.md 6.8 KB
- references/validation-and-recovery.md 3.9 KB
- references/variable-patterns.md 14 KB
- references/working-with-design-systems/wwds-components--creating.md 2.1 KB
- references/working-with-design-systems/wwds-components--using.md 2.5 KB
- references/working-with-design-systems/wwds-components.md 4.3 KB
- references/working-with-design-systems/wwds-effect-styles.md 3.6 KB
- references/working-with-design-systems/wwds-text-styles.md 5.4 KB
- references/working-with-design-systems/wwds-variables--creating.md 1.5 KB
- references/working-with-design-systems/wwds-variables--using.md 2.2 KB
- references/working-with-design-systems/wwds-variables.md 5.1 KB
- references/working-with-design-systems/wwds.md 5.1 KB
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 Changed · -50 lines cb559705302c
- 1mo ago Changed 06eb6927044a
- 1mo ago Changed · +2 lines 0480d6b537f1
- 1mo ago Changed · -7 lines 28220d2798e7
- 1mo ago First seen · 487 lines · 114 tokens per session scan A f0e172dd17c2
figma-use is a skill published in the GitHub repository PracticalSwan/agent-skills (21 stars, last pushed 6d ago), licensed MIT. It adds 114 tokens to every session and 8,741 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to figma-use, differing in 194 lines, and is treated as a copy.
Other skills, from other repositories
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
figma-build
Build a Figma design from code or a description — the reverse of figma-codegen. Reuses the connected file's existing design system (components, variables, styles) instead of drawing primitives with hardcoded values. Triggers whenever the user wants something created or updated IN Figma from code or a spec — e.g.…
refero-design
Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive design, typography, color, spacing, motion, icons, accessibility, copywriting, conversion, and anti-AI-slop work. Use this…
figma-variable-audit
Audit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).
codebase-index
Generate machine-readable index files in .ai/index/ (component inventory, uses/usedBy graph, stats) for AI agents. Triggers: index my codebase, build a relationship graph, what depends on what. Not an assessment; for library health use component-audit.