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 seaworld008/Commonly-used-high-value-skills --skill figma-implement-designgit clone --depth 1 https://github.com/seaworld008/Commonly-used-high-value-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/seaworld008/commonly-used-high-value-skills/figma-implement-design)<a href="https://agentmods.dev/skills/seaworld008/commonly-used-high-value-skills/figma-implement-design"><img src="https://agentmods.dev/badge/skills/seaworld008/commonly-used-high-value-skills/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/seaworld008/commonly-used-high-value-skills/figma-implement-design"><img src="https://agentmods.dev/badge/skills/seaworld008/commonly-used-high-value-skills/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.00034 | $0.02716 |
| Opus 5.5 | $0.00014 | $0.01086 |
| Sonnet 5.5 | $0.00007 | $0.00543 |
| Haiku 4.5 | $0.00003 | $0.00272 |
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
88% identical to figma-implement-design — 60 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Design
When to Use
Use this skill when the user wants to:
- implement a Figma frame or component in code
- translate a Figma node into production-ready UI
- match an existing design with high visual fidelity
- bridge design tokens and project conventions during implementation
Usage
Recommended flow:
identify target node
-> fetch design context and screenshot
-> gather assets
-> translate into project conventions
-> validate against Figma
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.
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 0: Set up Figma MCP (if not already configured)
If any MCP call fails because Figma MCP is not connected, pause and set it up:
- Add the Figma MCP:
codex mcp add figma --url https://mcp.figma.com/mcp
- Enable remote MCP client:
- Set
[features].rmcp_client = trueinconfig.tomlor runcodex --enable rmcp_client
- Set
- Log in with OAuth:
codex mcp login figma
After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
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.
What ships with it
5 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.
- 1mo ago Changed · -42 tokens per session 63066764bb4d
- 1mo ago First seen · 295 lines · 76 tokens per session scan A ddd13c636aa7
figma-implement-design is a skill published in the GitHub repository seaworld008/Commonly-used-high-value-skills (73 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 2,716 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to figma-implement-design, differing in 60 lines, and is treated as a copy.
Other skills, from other repositories
omh-frontend
This is an OMH frontend workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-visual-qa
This is an OMH visual-qa workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
vibe-ui-methodology
A set of design rules for creating HTML, CSS, SVG, visualisations, presentations, and PDFs with planned colours, patterns, design tokens, and accessibility checks.
web-design
Penguin visual language for generated web pages and app UIs — GitHub-style simplicity with a single blue accent, light and pure-black dark themes, design tokens, component and chat-interface recipes, plus an opt-in warm paper editorial theme.
proto-bot-getting-started
A first-conversation guide for starting an interface-prototyping task. It gathers the application, design rules, allowed changes, and preferred delivery format only as needed before producing an initial result.
proto-bot-ops
A workflow for turning an existing application into interface prototypes, implementing approved page changes, and collecting review evidence. It checks the real code, pages, components, data, and visual states instead of treating a design file as an integrated product.