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 skills add memi-design/design-skills --skill figma-usegit clone --depth 1 https://github.com/memi-design/design-skillsWrote 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/memi-design/design-skills/figma-use)<a href="https://agentmods.dev/skills/memi-design/design-skills/figma-use"><img src="https://agentmods.dev/badge/skills/memi-design/design-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/memi-design/design-skills/figma-use"><img src="https://agentmods.dev/badge/skills/memi-design/design-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.00025 | $0.01552 |
| Opus 5.5 | $0.00010 | $0.00621 |
| Sonnet 5.5 | $0.00005 | $0.00310 |
| Haiku 4.5 | $0.00003 | $0.00155 |
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 1mo 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/figma-use — Foundational Figma Canvas Skill
Base skill for all Figma operations. Teaches agents how Figma works — structure, Auto Layout, variables, MCP tools, and the mandatory self-healing loop. Load this before any /figma-* skill.
Freedom Level: High
Agents have full canvas read/write access but must follow the self-healing protocol and never create floating elements.
MCP Tool Decision Tree
This is the most important section. Choose the right tool for the job:
Writing to Canvas
What are you trying to do?
CREATE a design using existing components/tokens:
→ use_figma (Official MCP)
WHY: It understands your design system, returns Code Connect hints,
and produces structured output. ALWAYS try this first.
RUN raw Plugin API code (batch ops, custom logic):
→ typed Mémoire Figma actions
WHY: For operations use_figma doesn't support — complex scripts,
bulk modifications, conditional logic.
INSTANTIATE an existing component:
→ figma_instantiate_component (Console MCP)
WHY: Fastest way to create an instance of a known component.
Call figma_search_components first to get the nodeId.
CREATE variables in bulk:
→ figma_batch_create_variables (Console MCP)
WHY: 10-50x faster than individual figma_create_variable calls.
SET a single property:
→ figma_set_fills / figma_set_text / figma_resize_node
WHY: Surgical single-property changes.
Reading from Canvas
What do you need?
Design with code hints + screenshot:
→ get_design_context (Official MCP) ← PREFERRED
Returns: code, screenshot, Code Connect snippets, annotations
Visual screenshot only:
→ get_screenshot (Official MCP) or figma_take_screenshot (Console)
Node properties and structure:
→ get_metadata (Official MCP)
Design tokens/variables:
→ get_variable_defs (Official) or figma_get_variables (Console)
Component search:
→ figma_search_components (Console) — call at SESSION START
NOTE: nodeIds are session-scoped, never reuse from previous sessions
Code Connect mappings:
→ get_code_connect_map (Official MCP) — CHECK FIRST before creating
What ships with it
1 file 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.
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.
- 1mo ago First seen · 176 lines · 25 tokens per session scan A 90c113191a64
figma-use is a skill published in the GitHub repository memi-design/design-skills (7 stars, last pushed 29d ago), licensed MIT. It adds 25 tokens to every session and 1,552 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
theme-audit
Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure 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).
accessibility-per-component
Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.
ai-component-description
Write a six-section prose description (purpose, props, anti-patterns, composition, accessibility, examples) for a Figma component's description field so LLMs read it via MCP. Triggers: describe this component for AI, Figma MCP description. JSON metadata files: use metadata-schema-generator.
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.
component-decision-tree
Write "choosing between" pages (docs/choosing/) that route an intent to the right component via narrowing questions; YAML trees on request. Triggers: which component should I use, choose between X and Y, dialog vs drawer, selection guide. One chosen component: usage-guidelines.