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 ulises-jeremias/agent-toolkit --skill figmagit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/figma)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/figma"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/figma.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.00056 | $0.01122 |
| Opus 5 | $0.00028 | $0.00561 |
| Sonnet 5 | $0.00011 | $0.00224 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
figma 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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma MCP
Use the Figma MCP server for Figma-driven implementation. For setup and
debugging details (env vars, tool registration, verification), see
references/figma-mcp-config.md.
This is the entry-point skill for the Figma family. Switch to a more specialized skill once intent is clear:
| If the user wants to… | Use |
|---|---|
| Translate a Figma node into production code | figma-implement-design |
| Generate a full screen in Figma from code/description | figma-generate-design (opt-in pack — see docs/SKILLS.md) |
| Author Code Connect mappings | figma-code-connect-components |
Create reusable agent rules (CLAUDE.md/AGENTS.md) for a design system |
figma-create-design-system-rules |
| Create a brand-new Figma file | figma-create-new-file |
| Run JS in Figma via the Plugin API | figma-use (opt-in pack — see docs/SKILLS.md) |
| Generate/import a full library | figma-generate-library (opt-in pack — see docs/SKILLS.md) |
Figma MCP Integration Rules
These rules define how to translate Figma inputs into code for this project and must be followed for every Figma-driven change.
Required flow (do not skip)
- Run
get_design_contextfirst to fetch the structured representation for the exact node(s). - If the response is too large or truncated, run
get_metadatato get the high-level node map and then re-fetch only the required node(s) withget_design_context. - Run
get_screenshotfor a visual reference of the node variant being implemented. - Only after you have both
get_design_contextandget_screenshot, download any assets needed and start implementation. - Translate the output (usually React + Tailwind) into this project's conventions, styles and framework. Reuse the project's color tokens, components, and typography wherever possible.
- Validate against Figma for 1:1 look and behavior before marking complete.
What ships with it
2 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.
- 2d ago First seen · 99 lines · 56 tokens per session scan A 082616c0497b
figma is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,122 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
ui-ux-design
Create production-grade frontend interfaces with strong UX and visual craft. Use when building web components, pages, dashboards, forms, landing pages, modals, or any UI. Use when user says 'build a form', 'create a dashboard', 'design a component', 'make a landing page', or asks for UI/UX work. Use even when the user…
margaret-design
Figma bridge, both directions: generate a new Figma design or diagram from a prompt/spec, or pull an existing Figma file/selection into this codebase (as code, a design-context summary, a Code Connect link, or a motion implementation). Use when the user asks to create/generate something in Figma or FigJam, wants a…
adobe-express-spectrum-ui-ux
Build or review Adobe Express add-on panel UI with Spectrum patterns, stack selection guidance (raw SWC, swc-react, React Spectrum), Express theme setup, state and navigation design, and actionable UX quality checks. Use when implementing or auditing panel layouts, interaction states, multi-screen flows, and…
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
ui-styling
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns…
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.