What is setup-project?

A diagnostic workflow for checking a Unity–Figma bridge: the connection between Figma, an MCP sidecar server, and the Unity Editor. It checks the Figma access token, server setup, Unity connection, and asset configuration.

Use it when setting up the project, checking whether it is ready, or diagnosing problems with Figma exports and Unity asset workflows.

These separate connections can fail in ways that look similar, so checking them in order identifies which layer is blocking work. The resulting status report gives the next action to take.

How chav0/UnityFigmaMCP configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/chav0/UnityFigmaMCP/main/.claude/skills/setup-project/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/chav0/UnityFigmaMCP

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chav0/unityfigmamcp/setup-project/github.svg)](https://agentmods.dev/skills/chav0/unityfigmamcp/setup-project)

Your own site

<a href="https://agentmods.dev/skills/chav0/unityfigmamcp/setup-project"><img src="https://agentmods.dev/badge/skills/chav0/unityfigmamcp/setup-project/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/chav0/unityfigmamcp/setup-project"><img src="https://agentmods.dev/badge/skills/chav0/unityfigmamcp/setup-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 131 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,219 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 original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00131	$0.01219
Opus 5.5	$0.00052	$0.00488
Sonnet 5.5	$0.00026	$0.00244
Haiku 4.5	$0.00013	$0.00122

Measured 2mo ago against content hash 2e6e3a12213e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-project 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 2mo 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.

.claude/skills/setup-project/SKILL.md · 115 lines

How it starts

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

Setup Project — UnityFigmaMCP Environment Check

This skill runs a diagnostic sequence to verify that all parts of the UnityFigmaMCP bridge are properly configured and connected. It checks each layer of the stack and produces a clear status report with actionable next steps.

Why this matters

UnityFigmaMCP has three independent systems that need to be working together: the Figma API (token + network), the MCP sidecar server, and the Unity Editor plugin connected via SignalR. A problem in any layer blocks the entire workflow, and the symptoms can be confusing — so a structured check saves time.

Diagnostic sequence

Run these checks in order. Each step depends on the previous one succeeding, but continue through all steps even if some fail — the user needs the full picture.

Step 1 — Server, Figma token and Unity connection

Call status. One response covers three things:

figma.tokenConfigured / figma.tokenValid — whether FIGMA_ACCESS_TOKEN is set and actually works. tokenValid is true only after a real API call succeeded, so it catches expired and revoked tokens, not just missing ones. figma.user shows who it belongs to.
unity.editorConnected — whether a Unity Editor is attached to the SignalR hub, plus unity.hubUrl for the address the Editor plugin connects to.
protocolVersion and a hint naming the next concrete action when something is off.

If ready is true, both halves work. Otherwise note what failed and continue — the remaining checks are still informative.

Step 2 — Unity Editor round-trip

Call unity_get_pipelines.

status already reported whether an Editor is registered on the hub, but this is the first call that actually travels the full path — MCP → server → SignalR → Unity Editor and back — and returns data the Editor had to produce. A connected-but-wedged Editor (blocked on a modal dialog, mid-compile) shows up here and not in status.

Step 3 — Pipeline configuration

From the unity_get_pipelines response, check:

Are there any pipelines configured?
List each pipeline's ID and steps

Read the full file on GitHub · 115 lines

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.

2mo ago First seen · 115 lines · 131 tokens per session scan A 2e6e3a12213e

Subscribe to this mod's changes

setup-project is a skill published in the GitHub repository chav0/UnityFigmaMCP (11 stars, last pushed 25d ago), licensed MIT. It adds 131 tokens to every session and 1,219 once invoked, about $0.0005 per session on Opus 5.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.

Debugging Game development ai ai-agents dotnet figma figma-to-code mcp

setup-project next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
setup-projectchav0/UnityFigmaMCP	Skill	11	25d ago	MIT	A	131	Claude Code
minecraft-debug-mcpmoeru-ai/airi	Skill	51k	yesterday	MIT	A	68	Codex
performance-optimizationgamedev-skills/awesome-gamedev-agent-skills	Skill	6.9k	9d ago	Apache-2.0	A	121	Claude Code
diagnosing-bgs-problemshashgraph-online/awesome-codex-plugins	Skill	1.5k	yesterday	Apache-2.0	A	72	Claude Code, Codex
axiom-audit-spritekitCharlesWiltgen/Axiom	Skill	1.3k	yesterday	MIT	A	39	Codex
scenario-unity-gameplayscenario-labs/skills	Skill	3.2k	yesterday	MIT	A	108	Claude Code
scenario-unreal-gameplayscenario-labs/skills	Skill	3.2k	yesterday	MIT	A	121	Claude Code

UnityFigmaMCP: Skill for Claude Code