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 figma-implement-designgit 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-implement-design)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/figma-implement-design"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/figma-implement-design/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/ulises-jeremias/agent-toolkit/figma-implement-design"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/figma-implement-design.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.00092 | $0.02794 |
| Opus 5.5 | $0.00037 | $0.01118 |
| Sonnet 5.5 | $0.00018 | $0.00559 |
| Haiku 4.5 | $0.00009 | $0.00279 |
Grade A, and why
figma-implement-design 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.
This is a copy
86% identical to figma-implement-design — 42 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Design
Overview
This skill provides a structured workflow for translating Figma designs into production-ready code with pixel-perfect accuracy. It ensures consistent integration with the Figma MCP server, proper use of design tokens, and 1:1 visual parity with designs.
Skill Boundaries
- Use this skill when the deliverable is code in the user's repository.
- If the user asks to create/edit/delete nodes inside Figma itself, install the
opt-in
figma-usepack (seedocs/SKILLS.md). - If the user asks to build or update a full-page screen in Figma from code or
a description, install the opt-in
figma-generate-designpack (seedocs/SKILLS.md); it requiresfigma-use. - If the user asks only for Code Connect mappings, switch to
figma-code-connect-components. - If the user asks to author reusable agent rules (
AGENTS.md/CLAUDE.md), switch tofigma-create-design-system-rules.
Prerequisites
- Figma MCP server must be connected and accessible
- User must provide a Figma URL in the format:
https://figma.com/design/:fileKey/:fileName?node-id=1-2:fileKeyis the file key1-2is the node ID (the specific component or frame to implement)
- OR when using
figma-desktopMCP: User can select a node directly in the Figma desktop app (no URL required) - Project should have an established design system or component library (preferred)
Required Workflow
Follow these steps in order. Do not skip steps.
Step 1: Get Node ID
Option A: Parse from Figma URL
When the user provides a Figma URL, extract the file key and node ID to pass as arguments to MCP tools.
URL format: https://figma.com/design/:fileKey/:fileName?node-id=1-2
Extract:
- File key:
:fileKey(the segment after/design/) - Node ID:
1-2(the value of thenode-idquery parameter)
Note: When using the local desktop MCP (figma-desktop), fileKey is not passed as a parameter to tool calls. The server automatically uses the currently open file, so only nodeId is needed.
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 · 269 lines · 92 tokens per session scan A b0998ad1f5a2
figma-implement-design is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 2,794 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to figma-implement-design, differing in 42 lines, and is treated as a copy.
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…
vibe-to-ui
Design systems, motion, mood boards, spatial layout, visual assets, Design Context profiles, and a global Inspiration Library from screenshots, website URLs, inspiration images, music, or fuzzy aesthetic intent. Classifies page archetype, explores 3 product-aware directions before locking tokens (unless exact…
ndv-perceptual
Perceptual cognition module. Injects simultaneous read-as-rendered vision into any phase where visual or UX quality is a concern — implementation review, component assessment, UI audit steps within a larger workflow. Source: ndv-design (Pixel).
design-logo
Generate a commercial-grade SVG logo for a project by reading its codebase and iterating with the user.
figma
Read Figma design files, nodes, rendered images and comments via the Figma REST API. Use when the user mentions Figma, a figma.com file link, implementing a design as code, extracting design tokens / colors / spacing, or summarizing comments on a design.
ux-audit
Production-grade UX audit and design guidance skill. Transforms vague design feedback into actionable, implementable recommendations. Two modes: guide (principles + do/don't rules for modern interfaces) and review (structured audit with prioritized fixes). Covers task-first UX, information architecture, CRAP visual…