What is figma-manage-variables?

A tool for managing Figma variables, which are reusable values for design systems such as colors, spacing, and typography. It also manages variable collections and modes, such as light and dark themes.

Use it to create, update, rename, organize, or delete variables and collections; change scopes or code syntax; and add or rename theme modes.

It helps keep design values organized and lets you make targeted changes across a Figma file instead of editing each value separately.

figma-manage-variables — Skill for Claude Code by southleft

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 southleft/figma-console-mcp-skills --skill figma-manage-variables

Clone the repo

git clone --depth 1 https://github.com/southleft/figma-console-mcp-skills

Made for: Claude Code.

Or install figma-console-mcp-skills, the plugin that ships this one along with the rest of its 23 skills.

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/southleft/figma-console-mcp-skills/figma-manage-variables/github.svg)](https://agentmods.dev/skills/southleft/figma-console-mcp-skills/figma-manage-variables)

Your own site

<a href="https://agentmods.dev/skills/southleft/figma-console-mcp-skills/figma-manage-variables"><img src="https://agentmods.dev/badge/skills/southleft/figma-console-mcp-skills/figma-manage-variables/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/southleft/figma-console-mcp-skills/figma-manage-variables"><img src="https://agentmods.dev/badge/skills/southleft/figma-console-mcp-skills/figma-manage-variables.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 762 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00133	$0.00762
Opus 5	$0.00067	$0.00381
Sonnet 5	$0.00027	$0.00152
Haiku 4.5	$0.00013	$0.00076

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

Security

Grade A, and why

figma-manage-variables 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 12d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/batch-update-variables.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

manage-variables-figma — 92% identical, 14 lines differ

skills/figma-manage-variables/SKILL.md · 39 lines

How it starts

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

figma-manage-variables — variable / collection / mode CRUD

Incremental, surgical edits to a Figma variable system: create one or many, update values in bulk, rename, set scopes and code syntax, add/rename modes, and delete. All via use_figma, on any plan.

Skill boundaries

use_figma rules — load the official figma-use skill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-level await + return (no IIFE, no figma.closePlugin(); console.log is not returned), inputs inlined as const at the top of each script, colors in 0–1 range, load fonts before any text op, await figma.getNodeByIdAsync(...), and atomic errors (a failed script applies nothing — read the error, fix, retry).
From-scratch bootstrap → figma-setup-design-tokens. Code sync → figma-import-tokens / figma-export-tokens.

Workflow

Identify targets. Most ops need IDs. Get variableId/modeId/collectionId from the figma-export-tokens read script or get_variable_defs. Collections can also be looked up by name inside the script.
Pick the operation from references/variable-ops.md — it has a complete, copy-paste use_figma snippet for each: create collection, create variable, batch create, batch update, rename, set scopes, add/rename mode, delete.
Run via use_figma (skillNames: "figma-manage-variables"). For large value updates use scripts/batch-update-variables.js (10–50× faster than one-call-per-value).
Confirm. Every snippet returns the affected IDs/names. Read back with get_variable_defs to verify. For deletes, confirm with the user first — removing a collection deletes all its variables and unbinds anything referencing them.

Key rules

Colors are 0–1 range. Use hexToRgb for hex input.
Always set scopes on new variables — the default ALL_SCOPES pollutes every picker.
Set code syntax (setVariableCodeSyntax('WEB', '--token-name')) so design↔code naming lines up.
Renames are safe — they preserve values and existing bindings. Deletes are destructive.
Aliases: bind one variable to another with v.setValueForMode(modeId, figma.variables.createVariableAlias(targetVar)).

Read the full file on GitHub · 39 lines

Files

What ships with it

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

12d ago First seen · 39 lines · 133 tokens per session scan A ffd77a055d94

Subscribe to this mod's changes

figma-manage-variables is a skill published in the GitHub repository southleft/figma-console-mcp-skills (81 stars, last pushed 26d ago), licensed MIT. It adds 133 tokens to every session and 762 once invoked, about $0.0007 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 accessibility ai-tools claude design-systems design-tokens dtcg

design-to-code

Use this skill when translating UI/UX designs into production-ready frontend code. Handles design source ingestion (Figma, Sketch, Adobe XD, screenshots, design specs), design token extraction, component hierarchy mapping, responsive breakpoint strategy, accessibility-first implementation (WCAG 2.1 AA minimum)…

JPeetz/agent-skills · 184 tokens

design-md

Author/validate/export Google's DESIGN.md token spec files.

mateaix/mateclaw · 14 tokens

system-pitch

Write a design system investment pitch with a business case and ROI framing. Trigger when someone says: pitch the design system, make the case for the system, sell this to leadership, justify the investment, business case for design systems, why should we invest in a design system, or anything about building an…

murphytrueman/design-system-ops · 72 tokens

token-audit

Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…

murphytrueman/design-system-ops · 93 tokens

ai-component-description

Generate AI-optimised text descriptions for components, formatted for Figma's MCP server and LLM consumption. This produces prose descriptions in a six-section format (purpose, props, anti-patterns, composition, accessibility, examples), NOT JSON schemas or structured data files. Trigger when someone says: write…

murphytrueman/design-system-ops · 132 tokens

context-engine-builder

Generate a context engine — seven structured blueprint files (UX, UI, content, accessibility, ethical, technical, business intelligence) that encode everything an AI agent needs to work with a design system. This produces YAML infrastructure in .ai/context-engine/, NOT a health score or quality assessment. Trigger…

murphytrueman/design-system-ops · 135 tokens