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-sync-design-systemgit 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-sync-design-system)<a href="https://agentmods.dev/skills/punkadillo/figma-code-composer/figma-sync-design-system"><img src="https://agentmods.dev/badge/skills/punkadillo/figma-code-composer/figma-sync-design-system.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.00019 | $0.01364 |
| Opus 5 | $0.00010 | $0.00682 |
| Sonnet 5 | $0.00004 | $0.00273 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
figma-sync-design-system 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.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Design System Components
Name
figma:figma-sync-design-system - Sync design system components between Figma and code
Synopsis
Synchronize design system components between Figma and codebase using Code Connect mappings. Identifies gaps, generates missing components, updates existing ones, and creates bidirectional links between design and code.
Description
You are tasked with synchronizing a design system between Figma and the codebase using the Figma MCP server and Code Connect. This command analyzes both Figma components and code components to identify discrepancies and facilitate keeping design and code in sync.
Implementation
Inventories all Figma components via MCP server and scans codebase for component library. Compares component sets to identify missing, outdated, or unmapped components. Generates Code Connect configuration files to establish bidirectional mapping between Figma designs and code implementations.
Your Task
-
Inventory Figma Components:
- Use Figma MCP tools to list all components in the file
- Group components by category (buttons, inputs, cards, etc.)
- Identify component variants and properties
- Note component descriptions and documentation
-
Inventory Code Components:
- Scan the codebase for existing component library
- Identify component files and their exports
- Check for existing Code Connect configurations
- Map components to Figma equivalents
-
Analyze Gaps:
- Identify Figma components without code implementations
- Identify code components without Figma designs
- Note variant mismatches (Figma has variants code doesn't)
- Find naming inconsistencies
-
Create Sync Plan:
- Prioritize which components to sync first
- Determine if generating new code or updating existing
- Plan Code Connect mapping creation/updates
- Identify breaking changes that need migration
-
Execute Sync: Based on user preference, either:
- Generate missing components: Create code for Figma-only components
- Update existing components: Align code with Figma changes
- Create Code Connect mappings: Link existing code to Figma
- Document discrepancies: Report on mismatches without changing code
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 · 207 lines · 19 tokens per session scan A 89b99435a49e
figma-sync-design-system is a skill published in the GitHub repository punkadillo/figma-code-composer (3 stars, last pushed 18d ago), licensed MIT. It adds 19 tokens to every session and 1,364 once invoked, about $0.0001 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-03.
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.
ux-design
Create comprehensive UX design with user flows, wireframes, and design systems.
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
figma-build
Build a Figma design from code or a description — the reverse of figma-codegen. Reuses the connected file's existing design system (components, variables, styles) instead of drawing primitives with hardcoded values. Triggers whenever the user wants something created or updated IN Figma from code or a spec — e.g.…