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 southleft/figma-console-mcp-skills --skill figma-component-propertiesgit clone --depth 1 https://github.com/southleft/figma-console-mcp-skillsWrote 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/southleft/figma-console-mcp-skills/figma-component-properties)<a href="https://agentmods.dev/skills/southleft/figma-console-mcp-skills/figma-component-properties"><img src="https://agentmods.dev/badge/skills/southleft/figma-console-mcp-skills/figma-component-properties/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.
<a href="https://agentmods.dev/skills/southleft/figma-console-mcp-skills/figma-component-properties"><img src="https://agentmods.dev/badge/skills/southleft/figma-console-mcp-skills/figma-component-properties.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00158 | $0.01126 |
| Opus 5 | $0.00079 | $0.00563 |
| Sonnet 5 | $0.00032 | $0.00225 |
| Haiku 4.5 | $0.00016 | $0.00113 |
Grade A, and why
figma-component-properties 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- component-properties-figma — 88% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
figma-component-properties — define a component's API + instantiate it
Two related jobs:
- Author the component's property API — add/edit/delete
TEXT,BOOLEAN,INSTANCE_SWAP, andVARIANTproperties so the component exposes the right knobs (the Figma equivalent of a React component's props). - Use the component — create an instance and set its properties (label text, boolean toggles, variant selection, swapped sub-instances).
Skill boundaries
use_figmarules — load the officialfigma-useskill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-levelawait+return(no IIFE, nofigma.closePlugin();console.logis not returned), inputs inlined asconstat 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).- Reading a component's existing property definitions / state machine →
use
figma-analyze-component-setorfigma-deep-component. - These are design-system authoring writes the native MCP's
get_design_context/get_metadata(read-only) do not cover.
Property types
| Type | What it controls | defaultValue |
Notes |
|---|---|---|---|
TEXT |
A text-layer string override | "Label" |
Bind in UI to a text node's characters |
BOOLEAN |
Show/hide a layer | true/false |
Bind to a layer's visibility |
INSTANCE_SWAP |
Which sub-component fills a slot | a component key | Pass preferredValues to populate the picker |
VARIANT |
A variant axis (Size, State…) | one option string | Only meaningful on a COMPONENT_SET |
Workflow — authoring properties
- Target the COMPONENT_SET (or standalone COMPONENT). You cannot add properties to an individual variant — the script errors and tells you to use the parent set.
- Add with
scripts/add-property.js(use_figma,skillNames: "figma-component-properties"). SetNODE_ID,PROPERTY_NAME,PROPERTY_TYPE,DEFAULT_VALUE.addComponentPropertyreturns a name with a#idsuffix — capture it. - Edit / delete by reusing the same script's
editComponentProperty(name, {...})/deleteComponentProperty(name)calls (commented variants are in the script). Use the suffixed name returned at creation for edits/deletes of non-variant props. - Verify by re-reading
node.componentPropertyDefinitions(the script returns it).
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.
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 · 62 lines · 158 tokens per session scan A 3299bfc9289c
figma-component-properties is a skill published in the GitHub repository southleft/figma-console-mcp-skills (80 stars, last pushed 25d ago), licensed MIT. It adds 158 tokens to every session and 1,126 once invoked, about $0.0008 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.
Other skills, from other repositories
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)…
design-md
Author/validate/export Google's DESIGN.md token spec files.
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…
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…
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…
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…