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 skills/awdr74100/figwright/figma-buildnpx 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.svg" alt="Measured on agentmods" 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.00180 | $0.01611 |
| Opus 5 | $0.00090 | $0.00805 |
| Sonnet 5 | $0.00036 | $0.00322 |
| Haiku 4.5 | $0.00018 | $0.00161 |
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 6d 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 — 96 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.
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:
- The Figma file — its existing design system, which you'll reuse and bind to:
get_variable_defs→ the file's variables (colour / spacing / radius / typography) with names + values +hex. These are the tokens you bind to.scan_components/get_local_components→ existing components to instance rather than rebuild. Match the source UI pattern (a card, a list row, a nav, a button) to a component.get_styles→ shared paint / text / effect styles to apply.
- The source you were handed — when it's code, which stack and styling system (Tailwind / Chakra / MUI / CSS modules / vanilla …) and whether it has a config / theme / tokens file. That's where its real values live — read them from there, don't assume a default.
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.
- 6d ago First seen · 96 lines · 180 tokens per session scan A 810f8c9d2c62
figma-build is a skill published in the GitHub repository awdr74100/figwright (679 stars, last pushed yesterday), licensed MIT. It adds 180 tokens to every session and 1,611 once invoked, about $0.0009 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 skills, from other repositories
figma-design-handoff
Figma-to-code design handoff patterns including Figma Variables to design tokens pipeline, component spec extraction, Dev Mode inspection, Auto Layout to CSS Flexbox/Grid mapping, and visual regression with Applitools. Use when converting Figma designs to code, documenting component specs, setting up design-dev…
favicon-exporter
Prepare and export favicon assets from Figma in common web sizes and formats.
padding-maker
Normalize spacing and padding in Figma layouts using auto layout where appropriate.
component-builder
Build reusable Figma components and variants with consistent auto layout and properties.
icon-exporter
Export consistent icon assets from Figma with useful names and formats.
accessibility
Audit and improve Figma designs for accessible contrast, typography, touch targets, and structure.