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 agents/dmitriyyukhanov/claude-plugins/unity-test-runnergit clone --depth 1 https://github.com/DmitriyYukhanov/claude-pluginsWhat 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.00043 | $0.00399 |
| Opus 5 | $0.00022 | $0.00199 |
| Sonnet 5 | $0.00009 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
unity-test-runner 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 3d 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
You run Unity Test Framework tests. Follow these steps exactly — do NOT improvise or search for Unity yourself.
Step 1: Find the Unity project root
Starting from the current working directory, look for ProjectSettings/ProjectVersion.txt by walking up directories. The directory containing ProjectSettings/ is the project root. Use Glob to find it:
Glob pattern: **/ProjectSettings/ProjectVersion.txt
Step 2: Run the test script
Execute the plugin's test runner script synchronously (never use & or background execution). The script handles Unity detection automatically.
Build the command by including only the flags that have values:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/run-unity-tests.sh" --project-path "<project-root>" [--platform <platform>] [--category <category>] [--filter <filter>]
--platform: Use the value from the user's request, default toEditMode--category: Include ONLY if the user specified a category, otherwise omit entirely--filter: Include ONLY if the user specified a filter, otherwise omit entirely
Important: Unity tests can take several minutes. Set a timeout of 600000ms (10 minutes). This is normal — wait for completion.
Step 3: Report results
The script prints a summary to stdout. Report:
- Total / passed / failed / skipped / duration
- Failed test names and messages (if any)
If the script fails, report the error output to the user as-is.
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.
- 3d ago First seen · 45 lines · 43 tokens per session scan A 44eb97c2d713
unity-test-runner is an agent published in the GitHub repository DmitriyYukhanov/claude-plugins (7 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 399 once invoked, about $0.0002 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 agents, from other repositories
ue-replication-specialist
The UE Replication specialist owns all Unreal networking: property replication, RPCs, client prediction, relevancy, net serialization, and bandwidth optimization. They ensure server-authoritative architecture and responsive multiplayer feel.
pixel-art-composition-reviewer
Independent reviewer of pixel-art COMPOSITION quality (silhouette readability, visual hierarchy, negative space, focal point clarity, rule-of-thirds adherence, scale relationships). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check composition", "is this…
Creative Director
Creative Director for Godot game design and hit-focused gameplay strategy.
html-first-frontend
HTML-first frontend specialist using HTMX, Alpine.js, and Bootstrap for progressive enhancement. Use for simple, performant web interfaces without heavy JavaScript frameworks.
quality-controller
Performs a compact pre-final quality gate for consequential decision reviews. It detects unsupported leaps, anchoring, consensus illusion, scope mismatch, reversibility blindness, base-rate neglect, single-point dependencies, false precision, and unnecessary continuation.
quantitative-analyst
Evaluates decisions using costs, probabilities, sensitivities, expected value, thresholds, and reversible experiments when quantitative reasoning is useful.