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/arktarusov/unity-cli-plugin/unity-cli-corenpx skills add ArkTarusov/unity-cli-plugin --skill unity-cli-coregit clone --depth 1 https://github.com/ArkTarusov/unity-cli-pluginWhat 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.00105 | $0.01694 |
| Opus 5 | $0.00053 | $0.00847 |
| Sonnet 5 | $0.00021 | $0.00339 |
| Haiku 4.5 | $0.00011 | $0.00169 |
Grade A, and why
unity-cli-core 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UnityCLI core
UnityCLI is a standalone unity binary from Unity Technologies (experimental, first public betas in 2026). It replaces the Unity Hub CLI and adds live control of a running Unity Editor. It is NOT Unity.exe (the editor binary with -batchmode flags) and NOT Unity Hub.
Two other skills cover the specialized halves:
- unity-editors — installing editors/modules, licenses, projects (Hub replacement)
- unity-pipeline — driving a running Editor (build, test, play mode, scene/asset commands)
Locating the binary — check before concluding it is missing
The tool is real even if you have no prior knowledge of it: it shipped after most model knowledge cutoffs. command not found almost always means a stale shell PATH, not a missing tool.
- Windows: binary at
%LOCALAPPDATA%\Unity\bin\unity.exe. The installer adds that dir to the user PATH — long-lived shells (agent harnesses, old terminals) don't see it. Fix for the current session:$env:Path += ";$env:LOCALAPPDATA\Unity\bin" - macOS/Linux: the install script updates the shell profile; run
command -v unityin a fresh login shell or source the profile. - Do NOT search Unity Hub folders,
Editor/folders, or npm — the CLI lives in none of them. - If genuinely absent: do not install it yourself — see "Installs require user consent" below.
Verify with unity --version (e.g. 1.0.0-beta.3).
Installs require user consent
Two separate things get installed, and they solve different problems:
| What | Scope | Enables | Install |
|---|---|---|---|
| UnityCLI binary | per machine | Installing/opening editors, managing projects, licenses — no running-Editor control | script from https://docs.unity.com/en-us/unity-cli/use-unity-cli |
Unity Pipeline package (com.unity.pipeline) |
per Unity project | Controlling a running Editor: unity command, play mode, live builds/tests (skill unity-pipeline) |
unity pipeline install |
The CLI alone is enough for editor/project management. Editor control needs both.
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 · 92 lines · 105 tokens per session scan A 12bfb3bd2a1a
unity-cli-core is a skill published in the GitHub repository ArkTarusov/unity-cli-plugin (6 stars, last pushed 15d ago), licensed MIT. It adds 105 tokens to every session and 1,694 once invoked, about $0.0005 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
particles
Use this skill when creating particle effects in Phaser 4. Covers ParticleEmitter, emission zones, death zones, particle properties, textures, gravity wells, and particle movement. Triggers on: particles, emitter, particle effect, explosion, fire, smoke.
web-games
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
ship-web-games
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.
unity
Compile, test, and drive Unity for this repo's C# packages (unity/core, jint, quickjs, clearscript) and the two Unity projects (tests/, kitchen-sink/). Use when a change touches C# under unity/, when Unity test results are needed, when a rendering snapshot has to be checked or regenerated, or when the app has to be…