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/inspect-diffnpx skills add chav0/UnityFigmaMCP --skill inspect-diffgit clone --depth 1 https://github.com/chav0/UnityFigmaMCPWhat 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.00107 | $0.00788 |
| Opus 5 | $0.00053 | $0.00394 |
| Sonnet 5 | $0.00021 | $0.00158 |
| Haiku 4.5 | $0.00011 | $0.00079 |
Grade A, and why
inspect-diff 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 yesterday.
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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inspect Diff — Figma vs Unity Comparison
This skill compares a Unity prefab with its Figma source node and produces a detailed diff report. Nothing is modified — this is purely read-only inspection. Use it to understand what's out of sync before deciding whether to update.
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
Workflow
Step 1 — Fetch both sides
Do these in parallel:
figma_get_node+figma_get_node_names— current Figma treeunity_get_hierarchy— current Unity prefab hierarchy
Step 2 — Compare
Walk both trees in parallel and compare by matching node names/paths.
Check these categories:
Structure:
- Nodes in Figma but not in Unity (added in design)
- Nodes in Unity but not in Figma (removed in design, or added manually in Unity)
- Sibling order differences
Text properties:
- Content, font size, font family, font style, color, alignment
RectTransform:
- Size (width, height), position, anchors, pivot
Image:
- Color, sprite reference, image type
Layout:
- Layout mode, spacing, padding, child alignment
ContentSizeFitter:
- Horizontal/vertical fit modes
Active state:
- Enabled/disabled mismatches
Step 3 — Report
Present in the user's language. Group by severity — structural changes first, then property changes.
## Figma vs Unity — Diff Report
Prefab: Assets/UI/Prefabs/MyScreen.prefab
Source: figma.com/file/<key>, node 123:456
### Summary
- 2 structural changes
- 5 property changes
- Prefab is NOT up to date
### Structural differences
Added in Figma (missing in Unity):
- Card/Badge
- Footer/SocialLinks
Only in Unity (not in Figma):
- Card/CustomOverlay — possibly added manually
### Property differences
| Node | Property | Figma | Unity |
|----------------|------------|--------------|--------------|
| Header/Title | text | "New Title" | "Old Title" |
| Header/Title | fontSize | 18 | 16 |
| Header/Title | color | #111111 | #333333 |
| Card | width | 320 | 300 |
| Content | spacing | 12 | 8 |
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.
- yesterday First seen · 110 lines · 107 tokens per session scan A e4db5db327df
inspect-diff is a skill published in the GitHub repository chav0/UnityFigmaMCP (2 stars, last pushed 17d ago), licensed MIT. It adds 107 tokens to every session and 788 once invoked, about $0.0005 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
mcp-sdk-audit
Upgrade @modelcontextprotocol/server (the MCP TypeScript SDK v2) and prove the wire contract survived. The SDK is a runtime dependency whose breakage lands on the wire, not in the type checker — so this sorts each release by which SDK source files it touched (Figwright uses only the server + stdio slice of a…
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.…
PuerTS Agent Development Guide
Guide for developing LLM agents based on PuerTsAgent framework — covers resource directory structure, system-prompt, skills, builtin modules, and best practices.
Install PuerTS for Unity
Guide for downloading and installing PuerTS UPM packages into a Unity project — covers version selection, package dependencies, download/extract and git URL installation methods, and Editor Assistant setup.