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 agentmods add skills/chav0/unityfigmamcp/update-prefabnpx skills add chav0/UnityFigmaMCP --skill update-prefabgit 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/update-prefab)<a href="https://agentmods.dev/skills/chav0/unityfigmamcp/update-prefab"><img src="https://agentmods.dev/badge/skills/chav0/unityfigmamcp/update-prefab.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 | $0.00110 | $0.01321 |
| Opus 5 | $0.00055 | $0.00660 |
| Sonnet 5 | $0.00022 | $0.00264 |
| Haiku 4.5 | $0.00011 | $0.00132 |
Grade A, and why
update-prefab 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 4d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Prefab — Sync with Figma Source
This skill compares an existing Unity prefab with its Figma source node and applies the differences. It handles structural changes (added/removed children) and property changes (text content, colors, sizes, fonts, layout settings). Sprites are not modified — only properties and structure.
When to use
The designer made changes in Figma and the developer needs to bring the Unity prefab in sync. Rather than rebuilding from scratch (which would lose any manual Unity-side tweaks), this skill applies only the delta.
Input
The user needs to provide:
- Prefab path — Unity asset path (e.g.
Assets/UI/Prefabs/MyScreen.prefab) - Figma file key — the key from the Figma URL
- Node ID — the Figma node this prefab was built from
If the user doesn't know the node ID, they may need to look it up in Figma.
If the prefab was built with /build-prefab, the node ID might be discoverable
from the component map via unity_list_assets with kind: "prefab".
Workflow
Step 1 — Fetch both sides
Do these in parallel:
figma_get_node+figma_get_node_names— get the current Figma treeunity_get_hierarchy— get the current Unity prefab hierarchy
Step 2 — Compare
Walk both trees and identify differences:
Structural changes:
- Nodes present in Figma but missing in Unity → need to be created
- Nodes present in Unity but missing in Figma → candidates for removal (ask the user before deleting — they might be intentional Unity-side additions)
Property changes per node (compare by matching node names/paths):
- Text: content, font size, font family, font style, color, alignment
- RectTransform: size, position, anchors, pivot
- Image: color, sprite path, image type
- Layout: layout mode, spacing, padding, alignment
- ContentSizeFitter: horizontal/vertical fit modes
- Active state: enabled/disabled
Step 3 — Present the diff
Before applying anything, show the user what will change. Group by change type:
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.
- 4d ago First seen · 153 lines · 110 tokens per session scan A 58ac68434398
update-prefab is a skill published in the GitHub repository chav0/UnityFigmaMCP (2 stars, last pushed 19d ago), licensed MIT. It adds 110 tokens to every session and 1,321 once invoked, about $0.0006 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-typings-audit
Upgrade @figma/plugin-typings and absorb what the new version exposes. Diffs the .d.ts between the installed and the target version (that package ships no changelog), sorts the changes into breakage / new API / silently-added fields, maps each onto the sandbox handlers, the hand-written Zod mirrors in shared, and the…
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.…
webui-design
このドキュメントは moorestech Web UI の見た目・構造のホワイトリストである。.
canicode-roundtrip
Run the full design-to-code roundtrip — analyze a Figma design, surface gotchas, write designer answers back into the file via the Figma Plugin API (usefigma), re-analyze to confirm the gotchas were captured, hand off to figma-implement-design, then optionally register a Code Connect mapping pointing the Figma…
canicode
Analyze a Figma design for development-friendliness and AI-friendliness — produces a graded readiness report listing rule-based issues with severity, affected nodes, and fix suggestions. Read-only: this skill never modifies the Figma file. TRIGGER when: the user shares a figma.com/design/... URL and asks to analyze…