Borrowing it
Nothing to install: this file belongs to chav0/UnityFigmaMCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chav0/UnityFigmaMCP/main/.claude/skills/download-sprites/SKILL.mdgit clone --depth 1 https://github.com/chav0/UnityFigmaMCPWrote 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/chav0/unityfigmamcp/download-sprites)<a href="https://agentmods.dev/skills/chav0/unityfigmamcp/download-sprites"><img src="https://agentmods.dev/badge/skills/chav0/unityfigmamcp/download-sprites.svg" alt="Measured on agentmods" height="20"></a>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.00070 | $0.01062 |
| Opus 5 | $0.00035 | $0.00531 |
| Sonnet 5 | $0.00014 | $0.00212 |
| Haiku 4.5 | $0.00007 | $0.00106 |
Grade A, and why
download-sprites 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 7d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Download Sprites — Figma to Unity
This skill exports image nodes from Figma as PNGs and imports them into the Unity project as sprite assets. Each sprite is automatically registered in the FigmaSpriteMap for use during prefab building.
When to use
The user wants to get specific images out of Figma and into Unity — icons, backgrounds, illustrations, or any visual element that should become a sprite asset rather than being built from primitives. This is a bulk-download workflow, not a single-image export.
Prerequisites
Before starting, verify the basics are in place (don't run the full setup-project check — just confirm the Figma token works and Unity is connected):
- Call
status—figma.tokenValidandunity.editorConnectedmust both be true - Call
unity_list_assetswithkind: "sprite"— shows what's already imported
If either fails, tell the user to run /setup-project first.
Workflow
Step 1 — Identify what to download
The user may provide sprites in different ways:
A) Figma file key + node ID(s):
The user gives specific node IDs. Fetch the node tree with figma_get_node and
figma_get_node_names to understand what they point at.
B) Figma file key + parent node ID: The user points to a frame or page that contains many sprites. Fetch the tree, show the node names to the user, and ask which ones to export — or export all leaf nodes / component instances.
C) A list of sprite names: The user has names but no IDs. They need to provide the Figma file key and a parent node ID so you can search the tree for matching names.
Step 2 — Check for duplicates
Call unity_list_assets with kind: "sprite" to get the current inventory. Compare against
the list of sprites to download. If some already exist, tell the user and ask
whether to skip or re-download them.
Step 3 — Download
Call unity_save_sprites (batch) with:
fileKey— the Figma file keysprites— array of{nodeId, spriteName}for each sprite to downloadscale— MUST be 1. Do NOT change this value. Only use a different scale if the user explicitly requests it.savePath— use the user's requested path, or omit to use the default from settings
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.
- 7d ago First seen · 114 lines · 70 tokens per session scan A d13a7fb533e9
download-sprites is a skill published in the GitHub repository chav0/UnityFigmaMCP (2 stars, last pushed 23d ago), licensed MIT. It adds 70 tokens to every session and 1,062 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-31.
Other skills, from other repositories
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
figma-build
Build a Figma design from code or a description — the reverse of figma-codegen. Reuses the connected file's existing design system (components, variables, styles) instead of drawing primitives with hardcoded values. Triggers whenever the user wants something created or updated IN Figma from code or a spec — e.g.…
biome-creation
A workflow for placing rocks, trees, plants, and other reusable scene objects into a Unity biome, a themed area of a game world. It also covers regenerating the biome and checking the result with screenshots.
before-after-audit
A before-and-after screenshot workflow for checking visual changes in a Unity scene. It keeps the Scene view camera fixed, compares the two images, and sends the difference for an external review.
design-pipeline
A build-and-test workflow for turning Figma designs into shadcn/ui components, a reusable set of interface components for React-based projects. It checks the result in a real browser at three screen sizes and runs accessibility checks.
vibefigma
Convert Figma designs to production-ready React components with Tailwind CSS. Use when user provides a Figma URL, asks to convert Figma designs to React/code, wants to extract components from Figma, or mentions "vibefigma". Requires a Figma access token (via --token flag, FIGMATOKEN env var, or .env file).