figma-to-code-mcp: Skill for OpenCode

.opencode/skills/figma-token-extraction/SKILL.md

figma-token-extraction is a skill for OpenCode from felixAnhalt/figma-to-code-mcp. It costs 25 tokens per session (472 once invoked), scanned A, original, MIT.

A tool for turning Figma design data into named design tokens, such as reusable colors, spacing, corner radii, shadows, and text styles. Figma is a design tool used to create interface layouts.

In plain words
What is it for?
Use it when converting Figma designs into code or organizing a design system.
Why use it?
It replaces repeated raw design values with a consistent set of reusable names and combines them with existing Figma variables.

Skill for OpenCode

Written for OpenCode: installed under .opencode/.

This is felixAnhalt/figma-to-code-mcp's own configuration. It tells OpenCode how to work on figma-to-code-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything figma-to-code-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to felixAnhalt/figma-to-code-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/felixAnhalt/figma-to-code-mcp/main/.opencode/skills/figma-token-extraction/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/felixAnhalt/figma-to-code-mcp

Made for: OpenCode.

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.

agentmods badge for figma-token-extraction

README.md
[![agentmods](https://agentmods.dev/badge/skills/felixanhalt/figma-to-code-mcp/figma-token-extraction/github.svg)](https://agentmods.dev/skills/felixanhalt/figma-to-code-mcp/figma-token-extraction)
Your own site
<a href="https://agentmods.dev/skills/felixanhalt/figma-to-code-mcp/figma-token-extraction"><img src="https://agentmods.dev/badge/skills/felixanhalt/figma-to-code-mcp/figma-token-extraction/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.

agentmods 80×15 button for figma-token-extraction

Your own site · 80×15
<a href="https://agentmods.dev/skills/felixanhalt/figma-to-code-mcp/figma-token-extraction"><img src="https://agentmods.dev/badge/skills/felixanhalt/figma-to-code-mcp/figma-token-extraction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 472 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00472
Opus 5.5 $0.00010 $0.00189
Sonnet 5.5 $0.00005 $0.00094
Haiku 4.5 $0.00003 $0.00047

Measured 2mo ago against content hash eaa9620fce6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

figma-token-extraction 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 2mo 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.

.opencode/skills/figma-token-extraction/SKILL.md · 52 lines

What it actually says

What I do

I know the full design token extraction pipeline in src/figma/tokenizer/.

Pipeline (in extractTokens() at src/figma/tokenizer/index.ts)

Step 1: Collect Figma variable refs

collectFigmaVarRefs() walks root + componentSets gathering _varRefs sidecars from Style and Layout objects. First-encountered name wins.

Step 2: Count frequencies

countFrequencies() (in frequencies.ts) tallies colors, spacings, radii, shadows, typographies, padding combos, heights. Var-bound values are skipped.

Step 3: Build semantic registries

buildSemanticTokenRegistry() (in registry.ts) assigns semantic names from frequency-ordered data. Categories:

  • Colors → COLOR_SEMANTIC_NAMES (primary, secondary, background, text, border, ...)
  • Shadows → SHADOW_SEMANTIC_NAMES (card, dropdown, modal, ...)
  • Spacings → auto-generated (spacingXs, spacingSm, ...)
  • Radii → auto-generated (radiusSm, radiusMd, ...)
  • Typographies → auto-generated (headingXl, body, caption, ...)
  • Padding combos → PADDING_COMBO_SEMANTIC_NAMES
  • Heights → auto-generated (heightSm, heightMd, ...)

Step 4: Build tokens registry

Merges invented tokens with Figma variable entries. Multiple Figma variables → same raw value → kept distinct.

Step 5: Replace raw values with token refs

replaceNodeTokens() and replaceComponentSetTokens() (in replace/) swap raw rgba/dimensions for { token: "category.name" } references.

Step 6: Strip _varRefs

stripVarRefsFromResponse() removes all _varRefs sidecars — must not appear in final output.

When to use me

Use this when:

  • Adding a new token category
  • Debugging token assignment
  • Understanding why a value got a particular semantic name
  • Modifying the tokenizer pipeline
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.

  1. 2mo ago First seen · 52 lines · 25 tokens per session scan A eaa9620fce6e

Subscribe to this mod's changes

figma-token-extraction is a skill published in the GitHub repository felixAnhalt/figma-to-code-mcp (7 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 472 once invoked, about $0.0001 per session on Opus 5.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-31.

Related

Other skills, from other repositories

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

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 52 tokens

glance-canonical-layouts

Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).

android/skills · 56 tokens

accessibility

Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.

microsoft/hve-core · 47 tokens