What is figma-design-system-sync?

A workflow for comparing a Figma design system with the matching code system. A design system is a shared set of colors, sizes, styles, components, and rules used across a product.

It helps find differences between what designers maintain in Figma and what developers maintain in code. It also outlines safe plans for mapping tokens and components without losing track of renames or deletions.

figma-design-system-sync — Skill for Codex by sergekostenchuk

Q: What is it for?

Auditing or planning changes to Figma variables, styles, components, variants, effects, assets, Code Connect links, and local code tokens.

Install

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.

Any agent

npx skills add sergekostenchuk/ui-ux-agent-skill-system --skill figma-design-system-sync

Clone the repo

git clone --depth 1 https://github.com/sergekostenchuk/ui-ux-agent-skill-system

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/figma-design-system-sync/github.svg)](https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/figma-design-system-sync)

Your own site

<a href="https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/figma-design-system-sync"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/figma-design-system-sync/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/figma-design-system-sync"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/figma-design-system-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 508 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00073	$0.00508
Opus 5	$0.00036	$0.00254
Sonnet 5	$0.00015	$0.00102
Haiku 4.5	$0.00007	$0.00051

Measured 11d ago against content hash 30f6a03b1f74, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

figma-design-system-sync 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 11d 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.

core/skills/figma-design-system-sync/SKILL.md · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Figma Design System Sync

Use this skill when Figma work touches reusable system contracts: variables, styles, components, variants, effects, assets, Code Connect, and local code tokens.

Modes

audit: compare Figma system artifacts to local code conventions.
sync-plan: plan variable/style/component updates.
token-map: map Figma variables to local tokens.
component-map: map components and variants to code components.
code-connect: create or review Code Connect files through the installed Figma skill.
governance: propose naming, versioning, and rollout rules.

Workflow

Read Figma context with figma-context-reader unless a current context brief exists.
Inspect the local code tokens/components before recommending sync actions.
If Code Connect is requested, invoke figma:figma-code-connect when present.
Build a diff: Figma source, code target, status, risk, and proposed change.
For mutations, route to figma-canvas-editor or figma-apply-effects with explicit scope.
Validate JSON/token outputs locally before treating them as evidence.

Guardrails

Do not rename or delete variables/components/styles without a migration map.
Do not treat generated code or generated variables as source of truth until reviewed.
Record which direction is authoritative for each artifact: Figma to code, code to Figma, or reconcile manually.
Keep variable binding promises compatible with current Figma Plugin API support.

Safety And Privacy

Treat unpublished tokens, library names, component inventories, and source component code as sensitive.
Do not push variable/component renames without an explicit migration map and rollback path.
Do not upload private token exports or component snapshots to external services without approval.

Output Shape

Use assets/design-system-sync-report.md.

Resources

Read $CODEX_SKILLS_DIR/senior-figma-orchestrator/references/figma-mcp-compatibility.md for current capability checks.

Read the full file on GitHub · 48 lines

Files

What ships with it

3 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.

Changes

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.

11d ago First seen · 48 lines · 73 tokens per session scan A 30f6a03b1f74

Subscribe to this mod's changes

figma-design-system-sync is a skill published in the GitHub repository sergekostenchuk/ui-ux-agent-skill-system (23 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 73 tokens to every session and 508 once invoked, about $0.0004 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-08-30.

Design and UX

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

figma-design-system-sync