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.
git clone --depth 1 https://github.com/ToshikiImagawa/unity-claude-code-toolsWrote 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.
[](https://agentmods.dev/commands/toshikiimagawa/unity-claude-code-tools/test)<a href="https://agentmods.dev/commands/toshikiimagawa/unity-claude-code-tools/test"><img src="https://agentmods.dev/badge/commands/toshikiimagawa/unity-claude-code-tools/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.
<a href="https://agentmods.dev/commands/toshikiimagawa/unity-claude-code-tools/test"><img src="https://agentmods.dev/badge/commands/toshikiimagawa/unity-claude-code-tools/test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00007 | $0.00314 |
| Opus 5.5 | $0.00003 | $0.00126 |
| Sonnet 5.5 | $0.00001 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
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.
What it actually says
/test Command
Execute Unity tests for the current Unity project.
Arguments
$ARGUMENTS
Optional arguments:
- Test mode:
EditMode,PlayMode, orAll(default) - Filter: Test name pattern to run specific tests
Usage Examples
/test
/test EditMode
/test PlayMode
/test All MyNamespace.MyTestClass
Execution
Follow the unity-test skill to execute the tests:
- Run the test script to check if Unity Editor is running
- Based on the mode:
- Batch mode (Editor closed): Tests run automatically via script, analyze with
test-resultagent - Editor mode (Editor open): Use Unity MCP's
run_teststool to execute tests directly
- Batch mode (Editor closed): Tests run automatically via script, analyze with
Expected Output
The test result will be displayed in one of these formats:
Success:
[TEST OK] Ran N tests. All passed.
Failure:
[TEST FAILED] M of N tests failed.
- {TestClass}.{TestMethod}: {FailureReason}
If tests fail, analyze the failure reasons and suggest fixes based on the error messages.
Notes
- When Unity Editor is open, tests are executed via Unity MCP
- Unity MCP must be installed in the Unity project for Editor mode
- If Unity MCP is not available, suggest closing Unity Editor to run in batch mode
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 · 57 lines · 7 tokens per session scan A aec031fd863f
test is a command published in the GitHub repository ToshikiImagawa/unity-claude-code-tools (2 stars, last pushed 9mo ago), licensed MIT. It adds 7 tokens to every session and 314 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
verify-pr
Verify a PR's frontend changes through browser automation.
test-run
Run E2E tests with qa-use CLI.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.