agentmods.dev

design-system-inventory-figma

design-system-inventory-figma is a skill for Claude Code from southleft/skills-for-figma. It costs 160 tokens per session (1,036 once invoked), scanned A, a copy of figma-design-system-inventory, MIT.

A Figma design-system inventory skill that collects variables, design tokens, components, component sets, and styles from an entire file. Design tokens are reusable values such as colors, spacing, and font sizes.

In plain words
What is it for?
Use it to prepare code generation, audit a Figma component library, or document the values and variants used across a design system.
Why use it?
It gives you one structured overview of a design system instead of requiring separate inspections of its colors, components, and styles. This helps reveal what exists before generating code or checking a library.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the skills-for-figma plugin — 18 skills shipped together

not rated 14repo +1 3mo ago A scan 160 tokens copy · 95% MIT

Good fit Use it to prepare code generation, audit a Figma component library, or document the values and variants used across a design system.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/southleft/skills-for-figma/design-system-inventory-figma
View source ↗ southleft/skills-for-figma
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/skills-for-figma --skill design-system-inventory-figma
Clone the repo
git clone --depth 1 https://github.com/southleft/skills-for-figma

Made for: Claude Code.

Or install skills-for-figma, the plugin that ships this one along with the rest of its 18 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.

agentmods badge for design-system-inventory-figma

README.md
[![agentmods](https://agentmods.dev/badge/skills/southleft/skills-for-figma/design-system-inventory-figma/github.svg)](https://agentmods.dev/skills/southleft/skills-for-figma/design-system-inventory-figma)
Your own site
<a href="https://agentmods.dev/skills/southleft/skills-for-figma/design-system-inventory-figma"><img src="https://agentmods.dev/badge/skills/southleft/skills-for-figma/design-system-inventory-figma/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 design-system-inventory-figma

Your own site · 80×15
<a href="https://agentmods.dev/skills/southleft/skills-for-figma/design-system-inventory-figma"><img src="https://agentmods.dev/badge/skills/southleft/skills-for-figma/design-system-inventory-figma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 160 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,036 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 95% copy Near-identical to another mod 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.00160 $0.01036
Opus 5 $0.00080 $0.00518
Sonnet 5 $0.00032 $0.00207
Haiku 4.5 $0.00016 $0.00104

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

Security

Grade A, and why

design-system-inventory-figma 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/inventory.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

This is a copy

95% identical to figma-design-system-inventory — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/design-system-inventory-figma/SKILL.md · 50 lines

How it starts

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

design-system-inventory-figma — unified tokens + components + styles extraction

A single use_figma call that walks the whole file and returns a structured kit: tokens (every local variable, grouped by collection and mode), components (standalone components + component sets, with property definitions and a compact visualSpec per variant), and styles (paint/text/effect styles with their resolved values). It is the "read everything once" front door for code generation and library audits.

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).
  • The exact shape of each visualSpec → references/visual-spec.md.
  • One component in unlimited depth (full tree, reactions, instance refs) → use deep-component-figma. One variant set as a CSS state machine → use analyze-component-set-figma. Token files on disk → use export-tokens-figma.
  • This is a whole-system design capability the native MCP does not have: get_design_context works on a single selection and get_metadata returns flat structure, neither gives a unified tokens+components+styles kit on ANY plan.

Workflow

  1. Pick scope & verbosity to control response size on big files. Edit the constants in scripts/inventory.js:
    • INCLUDE — any of "tokens", "components", "styles" (default: all three).
    • VERBOSITY — "full" (per-variant visual specs), "summary" (component metadata + props, no per-variant specs), or "inventory" (names/ids/counts only — for huge files).
    • COMPONENT_NAME_FILTER — substring to limit components (e.g. "Button").
  2. Run via use_figma (skillNames: "design-system-inventory-figma"). Reads variables through the Plugin API, so it works on every Figma plan (no Enterprise REST requirement).
  3. Consume. Use tokens for color/spacing/typography values, components[].properties for the component API, components[].variants[].visualSpec for per-state appearance, and styles for any style-based (non-variable) values.
  4. If the result is still large, drop to a lower VERBOSITY or narrow INCLUDE / COMPONENT_NAME_FILTER and re-run — don't try to page a giant full dump.

Read the full file on GitHub · 50 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.

  1. 12d ago First seen · 50 lines · 160 tokens per session scan A daec69ba39cf

Subscribe to this mod's changes

design-system-inventory-figma is a skill published in the GitHub repository southleft/skills-for-figma (14 stars, last pushed 3mo ago), licensed MIT. It adds 160 tokens to every session and 1,036 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to figma-design-system-inventory, differing in 10 lines, and is treated as a copy.

Design and UXagent-skillsdesign-systemsdesign-tokensfigmafigma-mcp
Related

Other skills, from other repositories

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

stakeholder-brief

Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…

murphytrueman/design-system-ops · 73 tokens

token-compliance

Check a codebase or implementation for token compliance — finding hardcoded values, wrong-tier token references, and inconsistent token application in consuming code. This checks how tokens are used in code, NOT how the tokens themselves are defined or structured. Trigger when someone says: are we using tokens…

murphytrueman/design-system-ops · 120 tokens