A command workflow for writing and running comprehensive Unity tests for a feature. It distinguishes EditMode tests for standalone logic from PlayMode tests that need Unity's object lifecycle.

Use it to identify test targets, create tests from Gherkin scenarios, check boundary cases, run the test suite, and route implementation failures to a debugging workflow.

It helps turn feature scenarios into tests, include edge cases, and report failures clearly instead of stopping after a narrow test run. Unity is a game-development platform and Gherkin scenarios are plain-language behavior descriptions.

uw-cmd-test — Command for Claude Code by devdavv/unity-ai-workflow

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.

Clone the repo

git clone --depth 1 https://github.com/devdavv/unity-ai-workflow

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/commands/devdavv/unity-ai-workflow/uw-cmd-test/github.svg)](https://agentmods.dev/commands/devdavv/unity-ai-workflow/uw-cmd-test)

Your own site

<a href="https://agentmods.dev/commands/devdavv/unity-ai-workflow/uw-cmd-test"><img src="https://agentmods.dev/badge/commands/devdavv/unity-ai-workflow/uw-cmd-test/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/commands/devdavv/unity-ai-workflow/uw-cmd-test"><img src="https://agentmods.dev/badge/commands/devdavv/unity-ai-workflow/uw-cmd-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 350 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.00000	$0.00350
Opus 5.5	$0.00000	$0.00140
Sonnet 5.5	$0.00000	$0.00070
Haiku 4.5	$0.00000	$0.00035

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

Security

Grade A, and why

uw-cmd-test 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 1mo 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-test.md · 47 lines

What it actually says

/uw-cmd-test — Testing Workflow

Write comprehensive tests for a feature and verify they all pass.

Skills

Load uw-unity-test-runner from .claude/skills/uw-unity-test-runner/SKILL.md.

Steps

1. Identify Test Targets

Which feature or system needs testing?
Find the relevant GDD Gherkin scenarios for this feature.
Check if tests already exist — avoid duplicates.

2. Generate Tests

EditMode tests for pure logic (no MonoBehaviour lifecycle).
PlayMode tests for systems that need Update/Awake/Start.
Map each Gherkin scenario to one or more test methods.

3. Edge Cases

Go beyond the GDD scenarios — test boundaries:

What happens with zero or negative values?
What happens at max capacity?
What happens with null inputs?
What happens with rapid repeated calls?

4. Run Tests

Via Unity MCP run_tests if available.

Capture results and report:

12/14 tests passed
FAILED: TakeDamage_WhenHealthIsZero_DoesNotGoNegative
FAILED: Shoot_WhenDisconnected_QueuesAction

5. Fix Failures

If tests fail due to implementation bugs, switch to /uw-cmd-debug.
If tests fail due to test errors, fix the test.
Re-run until all pass.

6. Output

Complete test suite with passing results
Test coverage summary
Any discovered bugs filed

$ARGUMENTS

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.

1mo ago First seen · 47 lines · 0 tokens per session scan A 815eec08afb8

Subscribe to this mod's changes

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

Claude Code Game development Testing Unit testing ai-workflow antigravity-ide game-development unity unity2d

game-arch

Design, refactor, test, or profile a game's code architecture.

HermeticOrmus/LibreGameDev-Claude-Code · 13 tokens

build-and-compilation

These commands drive the build/compile/test dev loop, plus build configuration: triggering Player builds and reading the resulting BuildReport, switching the active build target, enumerating targets, reading/writing EditorUserBuildSettings, and listing Build Profiles. Several commands are asynchronous: trigger the…

Alex-Rachel/TEngine · 0 tokens

uw-cmd-test