uw-cmd-setup-project

A setup workflow for starting a Unity game project with its folders, packages, version control, documentation, and development connections. It first asks whether the project should be built collaboratively or with minimal interruptions.

In plain words
What is it for?
Use it when creating a Unity project from scratch. It helps configure the project, check the environment, create folders, set up packages and Git, and record connections such as Unity or GitHub tools.
Why use it?
It gives a new project a consistent structure and records important choices such as the Unity version, development mode, and available tool connections.

Command for Claude Code

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.

agentmods
npx agentmods add commands/devdavv/unity-ai-workflow/uw-cmd-setup-project
Clone the repo
git clone --depth 1 https://github.com/devdavv/unity-ai-workflow

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 769 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00769
Opus 5 $0.00000 $0.00385
Sonnet 5 $0.00000 $0.00154
Haiku 4.5 $0.00000 $0.00077

Measured 2d ago against content hash 03359240ab03, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

uw-cmd-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 2d 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/commands/uw-cmd-setup-project.md · 82 lines

How it starts

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

/uw-cmd-setup-project — Project Setup Workflow

Initialize a new Unity project with all infrastructure: folders, packages, git, and MCP connections.

Skills

Load uw-unity-project-setup skill from .claude/skills/uw-unity-project-setup/SKILL.md.

Steps

0. Select Dev Mode

Ask the user before anything else:

"Which dev mode do you want for this project?

  • Guided (recommended default) — We collaborate. I suggest next steps and execute after you confirm key decisions.
  • Autonomous — Tell me your game idea and goals, I'll build the game with minimal interruptions. For best results, also enable Claude Code auto mode.

You can change it later in docs/ProjectConfig.yaml -> ai_mode."

If autonomous mode: Ask ALL onboarding questions now (pitch, platforms, genre, references, features, packages, MCP availability). Set ai_mode in ProjectConfig.

1. Verify Environment

  • Confirm Unity version matches ProjectConfig.
  • Ask about MCP availability (Unity MCP, GitHub MCP).
  • If install links needed, reference docs/MCP_SETUP.md — never guess URLs.
  • Update docs/ProjectConfig.yaml -> mcp section.

2. Create Folder Structure

Use uw-unity-project-setup skill:

  • Create Assets/_Project/ with standard subfolders.
  • Structure depends on folder_strategy from ProjectConfig.
  • Create Core.asmdef in root scripts folder.
  • Create Core.Tests.EditMode.asmdef in Tests/EditMode/ so the test runner skill has a test assembly from day one.

3. Install Packages

From docs/ProjectConfig.yaml -> packages:

  • Via Unity MCP manage_packages if available.
  • Manual fallback (no MCP): Write an editor script using UnityEditor.PackageManager.Client.Add() to install packages programmatically from a menu item. The user runs it once, then it can be deleted.
  • Install third-party from docs/ProjectConfig.yaml -> third_party.

4. Configure Editor Settings

Via Unity MCP if available:

  • Render pipeline (URP/HDRP/Built-in)
  • Color space: Linear
  • Scripting backend: IL2CPP
  • Target platform(s)

Read the full file on GitHub · 82 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. 2d ago First seen · 82 lines · 0 tokens per session scan A 03359240ab03

Subscribe to this mod's changes

uw-cmd-setup-project is a command published in the GitHub repository devdavv/unity-ai-workflow (41 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 769 tokens. 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-30.