Borrowing it
Nothing to install: this file belongs to Synerise/synerise-design. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Synerise/synerise-design/master/.claude/skills/figma-code-connect/SKILL.mdgit clone --depth 1 https://github.com/Synerise/synerise-designWrote 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/synerise/synerise-design/figma-code-connect)<a href="https://agentmods.dev/skills/synerise/synerise-design/figma-code-connect"><img src="https://agentmods.dev/badge/skills/synerise/synerise-design/figma-code-connect.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Supply Chain · line 50 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- medium Data Exfiltration · line 50 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00023 | $0.01867 |
| Opus 5 | $0.00012 | $0.00933 |
| Sonnet 5 | $0.00005 | $0.00373 |
| Haiku 4.5 | $0.00002 | $0.00187 |
Grade A, and why
figma-code-connect scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "X-Figma-Token: <token>" "https://api.figma.com/v1/files/fsSZONXpVvtrDsCgtu01Jb/component_sets" \ How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Generate a <ComponentName>.figma.tsx file that connects a React component to its Figma design using the @figma/code-connect library.
Arguments
The user must provide:
- Component name — e.g.,
Switch,Button,Avatar
The user may optionally provide:
- Figma URL — the Figma node URL for the component (from Figma dev mode)
- Figma variant properties and their values
- Which props map to which Figma properties
- Nested component props (e.g., Label, Description sub-layers)
Figma Design System File
- File key:
fsSZONXpVvtrDsCgtu01Jb - URL pattern:
https://www.figma.com/design/fsSZONXpVvtrDsCgtu01Jb/Synerise-Design-System?node-id=<nodeId>&m=dev
Workflow
Step 1 — Locate the component
Find the component source files:
packages/components/<component-name>/src/<ComponentName>.tsx
packages/components/<component-name>/src/<ComponentName>.types.ts
packages/components/<component-name>/src/index.ts
Read these files to understand:
- The component's props interface (from
.types.ts) - Named exports and default export (from
index.tsand the main component file) - What the component renders and how props affect it
Step 2 — Get Figma structure via MCP
If the Figma MCP server is available (tools like mcp__figma__get_design_context exist), use it to get the component details:
- If the user provided a Figma URL, extract
fileKeyandnodeIdfrom it. - If no URL was provided, search for the component using the Figma REST API:
curl -s -H "X-Figma-Token: <token>" "https://api.figma.com/v1/files/fsSZONXpVvtrDsCgtu01Jb/component_sets" \ | python3 -c "import sys,json; [print(json.dumps({...})) for cs in json.load(sys.stdin)['meta']['component_sets'] if '<name>' in cs['name'].lower()]" - Call
mcp__figma__get_design_contextwith thenodeIdandfileKeyto get design context, screenshots, and code suggestions. - If MCP suggests Code Connect mappings (via
get_code_connect_suggestions), follow the flow to map sub-components (like Button) and then use the returned design context.
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 · 152 lines · 23 tokens per session scan A cadca8134a44
figma-code-connect is a skill published in the GitHub repository Synerise/synerise-design (96 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,867 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
suanfish-design-system
A Chinese design system for creating and reviewing web interfaces, with multiple design perspectives working together. It focuses on React and Tailwind-based projects.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
design
Use when the user wants the visual/experiential design of a product done systematically — a design system, a screen, a landing page, or a visual identity — grounded in researched real-world prior art and free of AI slop. Establishes/extends the design system, invokes the matching local taste skill, dispatches the…
seed-design
An integration guide for SEED Design, covering shared component specifications and foundations plus React and Lynx implementation guidance.
ss-studio
Turn a product brief and optional references into three distinct creative directions, a human-selected StyleSeed interaction plan, generated image/video asset jobs, a working UI prototype, and a verified prototype-first showcase reel. Use for client concepts, app interaction exploration, trendy but coherent UI…
ss-lint
Quick automated lint — detects common design system violations in seconds.