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 alvinindra/figma-mcp-rust --skill generate-component-variantsgit clone --depth 1 https://github.com/alvinindra/figma-mcp-rustWrote 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/alvinindra/figma-mcp-rust/generate-component-variants)<a href="https://agentmods.dev/skills/alvinindra/figma-mcp-rust/generate-component-variants"><img src="https://agentmods.dev/badge/skills/alvinindra/figma-mcp-rust/generate-component-variants/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/alvinindra/figma-mcp-rust/generate-component-variants"><img src="https://agentmods.dev/badge/skills/alvinindra/figma-mcp-rust/generate-component-variants.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.00063 | $0.00798 |
| Opus 5 | $0.00032 | $0.00399 |
| Sonnet 5 | $0.00013 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
generate-component-variants 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Component Variants
Given an existing frame or component, produce a set of visual variants (e.g. sizes, color themes, states) by cloning and mutating it. Arrange the variants in a tidy grid for review.
Input
Ask the user:
- Source node ID (the base component or frame to clone)
- What variants to generate, one or more of: a) Sizes: Small, Medium, Large (scale width/height, adjust font size and padding) b) Color themes: e.g. Primary, Secondary, Danger, Success, Warning c) States: Default, Hover, Pressed, Disabled, Loading d) Dark mode: duplicate with inverted background/text colors
- Arrange output on same page or new frame? (default: new container frame)
Steps
1. Inspect the source
Call get_node(sourceNodeId) to understand:
- Width, height, position
- Fill colors (note hex values)
- Text content and sizes
- Child structure
2. Plan the variant grid
Calculate layout:
- Each clone = source width x source height
- Gap between clones = 24px
- Label each clone with its variant name (create_text node below each)
- Total container width = (cloneWidth + 24) x columns
3. Create container frame (if requested)
create_frame(name="Variants/ComponentName", width=totalWidth, height=totalHeight, layoutMode="HORIZONTAL", itemSpacing=24, paddingTop=32, paddingLeft=32, paddingRight=32, paddingBottom=32)
4. For each variant
Sizes:
- Clone source: clone_node(sourceId, parentId=containerId)
- Compute scale factor (SM=0.75, MD=1.0, LG=1.5)
- resize_nodes to new dimensions
- For TEXT children: set_text to same content (font size cannot be changed via MCP; note this limitation)
- rename_node to "ComponentName/SM" etc.
Color themes:
- Clone source: clone_node(sourceId, parentId=containerId)
- For each fill-bearing child: set_fills(nodeId, color=themeHex)
- Color mapping suggestion:
- Primary: use brand primary color
- Secondary: use brand secondary color
- Danger: #EF4444
- Success: #22C55E
- Warning: #F59E0B
- rename_node to "ComponentName/Primary" etc.
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.
- 10d ago First seen · 83 lines · 63 tokens per session scan A 0dc357371b6b
generate-component-variants is a skill published in the GitHub repository alvinindra/figma-mcp-rust (38 stars, last pushed 5d ago), licensed MIT. It adds 63 tokens to every session and 798 once invoked, about $0.0003 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
clean-interface-design
Design clean, calm, uncluttered interfaces that don't read as templated AI output. Use when building or restyling any UI (web, iOS, Android, macOS) and it needs visual hierarchy, restraint, spacing discipline, one clear primary action, and a cohesive look. Covers accent color, whitespace, corner radius, type scale…
landing-page-conversion
Build or improve landing pages and marketing sites that convert, not just look good. Use when writing a hero, structuring a page, choosing a CTA, adding social proof, or diagnosing why a page isn't converting. Covers positioning, copy-first workflow, the above-the-fold contract, page narrative, CTAs, trust, and…
ship-quality-gate
Run the deterministic auditors over a real project before it ships — design drift, security headers, generated-default tells, SEO/GEO signals, delivery signals, Apple and Android project configuration — and read the results correctly, disclosure list included. Use when someone asks "audit this", "is this ready to…
apple-platform-design
Design iOS, iPadOS, and macOS apps that feel native, in the Liquid Glass era. Use when building or reviewing Apple-platform UI — navigation, controls, sheets, materials, typography, haptics — or deciding what must change when porting from web/Android. Covers Apple's HIG, the Liquid Glass design language (iOS 26 /…
design-system-audit
Find out whether a codebase actually has a design system or is re-deciding the basics on every screen — count the distinct colors, sizes, radii, shadows and spacings, collapse the near-duplicates, and migrate onto tokens. Use when inheriting a codebase, before a redesign, when a UI "feels inconsistent but I can't say…
motion-and-animation
Add motion and animation that feels great, not like slop. Use when animating any UI — transitions, hovers, presses, sheets, drawers, modals, page transitions, gestures — or when an animation feels "off". Covers the easing rules agents get wrong (ease-out for enter, ease-in for exit), springs, interruptibility…