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 commands/devdavv/unity-ai-workflow/uw-cmd-testgit clone --depth 1 https://github.com/devdavv/unity-ai-workflowWhat 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.00000 | $0.00350 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
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 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.
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_testsif 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
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.
- 2d ago First seen · 47 lines · 0 tokens per session scan A 815eec08afb8
uw-cmd-test 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 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.
Other commands, from other repositories
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
cert-check
Review the current state against certification and platform compliance expectations.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
context
Activate a project phase context and align agents, commands, and priorities to it.
liveops-brief
Create a concise live operations brief for an event, offer, patch, or campaign.
adopt
Brownfield onboarding audit and migration plan.