uw-unity-project-setup

uw-unity-project-setup is a skill for Claude Code from IdoCohen560/claude-unity-game-studio. It costs 87 tokens per session (1,022 once invoked), scanned A, a copy of uw-unity-project-setup, MIT.

A setup guide for starting a Unity game project from a configuration file. It covers the project folders, packages, Git, and available tool connections.

In plain words
What is it for?
Use it to bootstrap a new Unity project, create standard folders and test assemblies, install configured packages, and prepare version control and tool connections.
Why use it?
It removes the need to create the initial project structure and setup steps by hand. It also checks that key project settings are filled in first.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to bootstrap a new Unity project, create standard folders and test assemblies, install configured packages, and prepare version control and tool connections.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/idocohen560/claude-unity-game-studio/uw-unity-project-setup
Install

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.

Any agent
npx skills add IdoCohen560/claude-unity-game-studio --skill uw-unity-project-setup
Clone the repo
git clone --depth 1 https://github.com/IdoCohen560/claude-unity-game-studio

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.

agentmods badge for uw-unity-project-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/uw-unity-project-setup/github.svg)](https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/uw-unity-project-setup)
Your own site
<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/uw-unity-project-setup"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/uw-unity-project-setup/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.

agentmods 80×15 button for uw-unity-project-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/uw-unity-project-setup"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/uw-unity-project-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,022 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.01022
Opus 5 $0.00044 $0.00511
Sonnet 5 $0.00017 $0.00204
Haiku 4.5 $0.00009 $0.00102

Measured 6d ago against content hash 473c292cae36, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

uw-unity-project-setup 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 6d 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.

Origin

This is a copy

100% identical to uw-unity-project-setup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

examples/my-first-game/.claude/skills/uw-unity-project-setup/SKILL.md · 95 lines

How it starts

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

Unity Project Setup

Orchestrate complete project initialization from ProjectConfig.yaml.

Before You Start

  1. Ensure docs/ProjectConfig.yaml is filled out.
  2. Unity project must be created and open in Editor.
  3. Check which MCP servers are available (Unity MCP for in-editor operations, GitHub for version control).

Steps (in order)

1. Verify ProjectConfig

Confirm Unity version, packages, folder strategy, networking choice.

Required fields — warn the user if any are missing or empty:

  • project_name
  • unity_version
  • render_pipeline
  • scripting_backend
  • folder_strategy

2. Create Folder Structure

Based on folder_strategy, create Assets/_Project/ with standard subfolders:

  • Core/Scripts/ + Core.asmdef
  • Core/Tests/EditMode/ + Core.Tests.EditMode.asmdef (so the test runner skill has a test assembly from day one)
  • Features/ or Scripts/ (depending on strategy)
  • Art/, Audio/, UI/, Prefabs/, Scenes/, Tests/

3. Install Packages

From ProjectConfig.yaml → packages, install via Unity MCP manage_packages if available.

Manual fallback (no MCP): Write an editor script (Editor/Setup/PackageInstaller.cs) using UnityEditor.PackageManager.Client.Add() to install packages programmatically. The user runs it once from the Unity menu, then it can be deleted.

4. Generate Core Utilities

  • GameDebug.cs via uw-unity-debugging skill
  • Add ENABLE_LOGS define for Development builds

5. Git Setup

  • Create .gitignore (Unity template)
  • Create develop branch
  • Initial commit
  • Use GitHub MCP if available, otherwise git CLI

6. Configure Editor

Via Unity MCP if available:

  • Render pipeline, color space (Linear), scripting backend (IL2CPP)

Manual fallback (no MCP): Write an editor script (Editor/Setup/ProjectConfigurator.cs) using PlayerSettings and GraphicsSettings APIs to set render pipeline, color space, scripting backend, and target platforms. Menu item under Tools > Project Setup > Apply Settings.

Read the full file on GitHub · 95 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.

  1. 6d ago First seen · 95 lines · 87 tokens per session scan A 473c292cae36

Subscribe to this mod's changes

uw-unity-project-setup is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (18 stars, last pushed 2mo ago), licensed MIT. It adds 87 tokens to every session and 1,022 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to uw-unity-project-setup, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

commit

One-shot conventional commit; bundled scripts adaptively gather diff context, draft the message, and stage+commit — pass ask to confirm first or add a hint for the title. Use only when the user asks for a commit.

foyzulkarim/skills · 49 tokens

pre-commit

Fast pre-commit quality gate: scans staged files for secrets, dead code, naming issues, merge conflict markers, and direct-to-main commits. Installs as a git hook via /pre-commit install.

RealDougEubanks/ClaudeMarketplace · 46 tokens

git-commit

Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have.".

thoughtbot/rails-consultant · 47 tokens

git-workflow

Enforces the release-branch Git model: scaffold feature branches, open PRs with review checks, cut releases with tags, and view workflow reference.

RealDougEubanks/ClaudeMarketplace · 34 tokens

release-notes

Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.

foyzulkarim/skills · 51 tokens

start-task

Bootstrap a task into a synced feature branch — one shot, zero confirmations. Detects the source from the args: GitHub issue ('#100', 'issue 100', 'gh issue 100', or bare '100'), Jira key ('PROJ-42'), or a local spec file path; ad-hoc conversation otherwise. Fetches the task, derives {type}/{number}/{slug}, syncs the…

foyzulkarim/skills · 125 tokens