Figwright is a two-way Model Context Protocol server that lets coding agents exchange information with Figma through a companion plugin, turning designs into framework-aware code and editing the Figma canvas from code. Developers use it with agents such as Claude Code, Cursor, or Codex to read design context and create or modify Figma elements, and the catalogue contains skills and other workflow components for those interactions.
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 awdr74100/figwright --skill figma-buildgit clone --depth 1 https://github.com/awdr74100/figwrightWrote 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/awdr74100/figwright/figma-build)<a href="https://agentmods.dev/skills/awdr74100/figwright/figma-build"><img src="https://agentmods.dev/badge/skills/awdr74100/figwright/figma-build/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/awdr74100/figwright/figma-build"><img src="https://agentmods.dev/badge/skills/awdr74100/figwright/figma-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00180 | $0.02233 |
| Opus 5.5 | $0.00072 | $0.00893 |
| Sonnet 5.5 | $0.00036 | $0.00447 |
| Haiku 4.5 | $0.00018 | $0.00223 |
Grade A, and why
figma-build 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
figma-build
Turn code or a description into a Figma design that looks like it belongs in the file: reuse the
components, variables, and styles that already exist, and only build what's genuinely missing. This
is the mirror image of figma-codegen — same "reuse beats regenerate / reference tokens not
literals" philosophy, pointed at the canvas instead of the codebase. This file is the router; deep
detail lives in references/ — load a reference when its step is in play.
You operate on the connected Figma file (the plugin's current session). There is no fetch-by-URL;
the user must have the target file open. Confirm a plugin is connected (ping) before building.
When to use
- The user wants to create or update something in Figma from code or a description — a screen, view, modal/dialog/drawer/sidebar/panel, a single component, or a design-system asset.
- Not for reading a Figma design into code — that's
figma-codegen.
More than one Figma file open
Every tool result says so when it applies, so you do not have to check up front: with two or more
files connected and none claimed, results carry a MORE THAN ONE FIGMA FILE IS OPEN block naming
them. It matters because calls otherwise follow whichever file the user last touched, which changes
when they switch tabs — so a task can read one file and write to another and report success.
When you see it, claim the file before doing anything else: list_files names every connected file,
use_file({ fileName }) claims one for this session (use_file({ sessionId }) when two open files
share a name — Figma allows that, and x (Copy) is how it happens). Every later call then reaches
that file whatever is in front, including while its tab sits in the background. If the user has not
said which file, ask — do not guess from the names.
First, understand the environment, then build (provider-first)
The write-side mirror of codegen's grounding, and the most important habit: an off-looking build almost always comes from invented values or assumed conventions. So understand this user's actual environment first, then build into it — never apply a generic template. There's no single "right" stack; there's their stack. Look at both ends before creating anything:
What ships with it
4 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.
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 · +13 lines 4a9f2a99d3af
- 8d ago Changed · +2 lines 74e39d2e80d5
- 14d ago Changed · +5 lines b44b2c2559cd
- 1mo ago Changed · +13 lines fc7e2b43a5bf
- 1mo ago First seen · 96 lines · 180 tokens per session scan A 810f8c9d2c62
figma-build is a skill published in the GitHub repository awdr74100/figwright (1,162 stars, last pushed today), licensed MIT. It adds 180 tokens to every session and 2,233 once invoked, about $0.0007 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-30.
Other skills, from other repositories
favicon-exporter
Prepare and export favicon assets from Figma in common web sizes and formats.
icon-exporter
Export consistent icon assets from Figma with useful names and formats.
padding-maker
Normalize spacing and padding in Figma layouts using auto layout where appropriate.
accessibility
Audit and improve Figma designs for accessible contrast, typography, touch targets, and structure.
component-builder
Build reusable Figma components and variants with consistent auto layout and properties.
design-tokens
Create and maintain coherent Figma variables and design-token systems.