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 skills/toshikiimagawa/unity-claude-code-tools/unity-testnpx skills add ToshikiImagawa/unity-claude-code-tools --skill unity-testgit clone --depth 1 https://github.com/ToshikiImagawa/unity-claude-code-toolsWhat 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.00027 | $0.00676 |
| Opus 5 | $0.00014 | $0.00338 |
| Sonnet 5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
unity-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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Test
Execute Unity tests and analyze the test results. Supports batch mode (when Editor is closed) and Unity MCP (when Editor is open).
When to Use
Use this skill when:
- User requests to run tests in a Unity project
- User wants to validate unit tests
- User runs the
/testcommand
Prerequisites
- Unity Editor must be installed via Unity Hub
- Current directory must be a valid Unity project (contains
Assets/folder) - Test assemblies must be properly configured in the project
- For MCP mode: Unity MCP must be installed and running in Unity Editor
Execution Steps
Step 1: Check if Unity Editor is running
Execute the test script to check the project state:
${CLAUDE_PLUGIN_ROOT}/scripts/unity-test.sh "$(pwd)" [test-mode] [filter]
The script outputs:
LOG_MODE:batch|editor
Step 2: Execute tests based on mode
If LOG_MODE is batch (Editor is closed)
The script will run tests in batch mode automatically. Extract:
LOG_FILE_PATH: Path to the log fileRESULT_FILE_PATH: Path to XML test results (if available)
Then call the test-result agent:
Task: test-result agent
Prompt: {log_file_path} batch
If LOG_MODE is editor (Editor is open)
Use Unity MCP to run tests directly in the Editor:
-
Run tests using MCP:
mcp__unity-mcp__run_testsThis returns a
job_idfor tracking the test execution. -
Poll for results:
mcp__unity-mcp__get_test_job with job_idKeep polling until the job is complete.
-
Report the results directly from the MCP response.
Test modes for MCP:
EditMode- Editor-based unit testsPlayMode- Runtime tests
Output Format
Success:
[TEST OK] Ran N tests. All passed.
Failure:
[TEST FAILED] M of N tests failed.
- {TestClass}.{TestMethod}: {FailureReason}
Error Handling
If the script fails to find Unity Editor:
- Inform the user that Unity is not installed or not found
- Suggest installing Unity via Unity Hub
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 · 103 lines · 27 tokens per session scan A 15ad1427791a
unity-test is a skill published in the GitHub repository ToshikiImagawa/unity-claude-code-tools (2 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 676 once invoked, about $0.0001 per session on Opus 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.
Other skills, from other repositories
gdunit-driver
Run gdUnit4 unit tests and parse results into structured output. Use this skill after writing or modifying code to verify correctness via unit tests, when diagnosing test failures, or when writing new test files. Triggers: "run tests", "test fails", "write a test", any gdUnit4/unit test mention. Supports both GDScript…
card-test
Canonical recipe for writing engine cast-pipeline tests. Use GameScenario + GameRunner::cast(...).resolve() and assert via CastOutcome deltas. Covers the six test-harness foot-guns (hand-written TargetRef vectors, incomplete modal target submission, wrong-point hand baseline, inline-keyword cards, AST-internal flag…
godot
Develop, test, build, and deploy Godot 4.x games. Use when working with Godot Engine, GDScript, GdUnit4 testing, PlayGodot automation, or exporting games to web/desktop. Covers CI/CD pipelines and deployment to Vercel/GitHub Pages/itch.io.
roblox-testing
Testing, debugging, and profiling Roblox experiences — Developer Console, Output, logging discipline, pcall and assertion patterns, TestEZ unit tests, the MicroProfiler (client and server), Scene Analysis, Script Profiler, memory diagnostics, network debugging, Luau type checking, and connection cleanup. Use when…
unity-testing
Unity 6 testing guide. Use when writing unit tests, integration tests, or doing TDD with Unity Test Framework. Covers Edit Mode and Play Mode tests, NUnit attributes ([Test], [UnityTest], [SetUp], [TearDown]), testing MonoBehaviours and coroutines, and CI/CD integration. Based on Unity 6.3 LTS documentation.
unity-tests-write
Use when writing Unity tests, including EditMode tests, PlayMode tests, performance testing, and code coverage.