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 punkadillo/figma-code-composer --skill figma-integrationgit clone --depth 1 https://github.com/punkadillo/figma-code-composerWrote 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/punkadillo/figma-code-composer/figma-integration)<a href="https://agentmods.dev/skills/punkadillo/figma-code-composer/figma-integration"><img src="https://agentmods.dev/badge/skills/punkadillo/figma-code-composer/figma-integration.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.00021 | $0.00934 |
| Opus 5 | $0.00010 | $0.00467 |
| Sonnet 5 | $0.00004 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
figma-integration 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 3d 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
100% identical to figma-integration — 0 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Integration Guidelines
You are an expert in integrating Figma designs with development workflows. Apply these guidelines when working with Figma designs and implementing them in code.
Design-to-Code Workflow
Extracting Design Information
- Identify component structure and hierarchy from Figma layers
- Extract color values, typography settings, and spacing values
- Note responsive behavior and breakpoint variations
- Document interactive states (hover, active, focus, disabled)
- Capture animation and transition specifications
Component Mapping
- Map Figma components to code components
- Identify reusable patterns and shared styles
- Document variant properties and their code equivalents
- Note auto-layout settings for flexbox/grid implementation
Implementation Guidelines
Colors and Theming
- Extract color values in appropriate formats (hex, rgb, hsl)
- Map Figma color styles to CSS custom properties or theme tokens
- Ensure color contrast meets accessibility standards
- Implement dark mode variants when specified
Typography
- Extract font families, weights, and sizes
- Map Figma text styles to CSS typography classes
- Implement responsive typography scaling
- Preserve line-height and letter-spacing values
Spacing and Layout
- Convert Figma auto-layout to CSS Flexbox or Grid
- Extract padding and margin values
- Implement consistent spacing scale
- Handle responsive layout changes at breakpoints
Components and Variants
- Create component variants matching Figma structure
- Implement interactive states consistently
- Document prop interfaces based on Figma properties
- Ensure component composition matches design intent
Asset Handling
Images and Icons
- Export images at appropriate resolutions (1x, 2x, 3x)
- Use SVG format for icons and simple graphics
- Implement lazy loading for large images
- Optimize file sizes for web performance
Exporting Best Practices
- Use consistent naming conventions for exports
- Organize assets in logical folder structures
- Document asset usage and context
- Version control design assets appropriately
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.
- 3d ago First seen · 165 lines · 21 tokens per session scan A 67b1343cfd24
figma-integration is a skill published in the GitHub repository punkadillo/figma-code-composer (3 stars, last pushed 18d ago), licensed MIT. It adds 21 tokens to every session and 934 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to figma-integration, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
ui-first-builder
Creates production-ready UI immediately from any description. Generates complete pages, components, and realistic mock data in FIRST response. Uses Next.js 16 + Tailwind + shadcn/ui. Never asks questions - infers everything from context. Triggers: UI creation, page building, component generation, build interface…
component-design
Apply a coherent visual system, responsive behavior, interaction states, and accessibility to Kun components.
coss-ui
Set up or extend a Next.js web app with Coss/UI — the official Cal.com design system, built on Base UI + Tailwind CSS v4 and installed through the shadcn CLI via the namespaced @coss/ registry. Two modes: Init (shadcn init @coss/style on a new project) and Add (pull @coss/ui primitives, single @coss/ components, or…
animated-icons
Add a Motion-animated icon to a Next.js app from a shadcn registry instead of hand-animating an SVG. Two registries, picked from the project's icon set: heroicons-animated (316 icons, shadcn add @heroicons-animated/ ) and hugeicons-animated (165 icons, shadcn add @hugeicons-animated/ , which also installs a shared…