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/bigdra50/unity-cli/unity-buildnpx skills add bigdra50/unity-cli --skill unity-buildgit clone --depth 1 https://github.com/bigdra50/unity-cliWhat 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.00058 | $0.00541 |
| Opus 5 | $0.00029 | $0.00270 |
| Sonnet 5 | $0.00012 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
unity-build 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 yesterday.
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
unity-build
PREREQUISITE:
../unity-shared/SKILL.md（Relay Server 経由で Unity Editor が起動/アクティブであること）skill 経由のコマンドは必ず
-i <instance>を付ける (unity-shared #インスタンス指定)。
ワークフロー
1. /unity-verify Quick Verify コンパイルエラーがないことを確認
2. ビルド設定確認 u -i <instance> build settings --json
3. ビルドシーン確認 u -i <instance> build scenes --json
4. ビルド実行 u -i <instance> build run --target <platform> --output <path>
5. 結果確認 成功/失敗を報告
コマンド
u -i <instance> build settings --json # 現在の設定
u -i <instance> build scenes --json # ビルドシーン一覧
u -i <instance> build run --target StandaloneWindows64 --output ./Build # ビルド実行
プラットフォーム
| target | 値 |
|---|---|
| Windows | StandaloneWindows64 |
| macOS | StandaloneOSX |
| Android | Android |
| iOS | iOS |
| WebGL | WebGL |
エラー対応
| エラー | 対応 |
|---|---|
| コンパイルエラー | /unity-verify で修正ループ |
| Missing Scene | u -i <instance> build scenes で確認、シーンパス修正 |
| プラットフォーム未対応 | u -i <instance> api call UnityEditor.EditorApplication ExecuteMenuItem --params '["File/Build Settings"]' |
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.
- yesterday First seen · 57 lines · 58 tokens per session scan A 5db541d14508
unity-build is a skill published in the GitHub repository bigdra50/unity-cli (39 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 541 once invoked, about $0.0003 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-30.
Other skills, from other repositories
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…
uloop-execute-dynamic-code
Execute C# with Unity APIs when existing uloop tools cannot inspect or edit enough. Use for reachable scene/component state, scene/prefab/menu automation, and PlayMode checks.
uloop-simulate-mouse-input
Simulate Mouse.current input in PlayMode through Unity Input System. Use for gameplay mouse clicks, long-press (LongPress), movement delta (MoveDelta/SmoothDelta), or scroll. Use --dry-run to check what a Game View coordinate hits in 3D physics before clicking (works in EditMode; no Input System required). Use…
uloop-pause-point
Pauses Unity playback at any source file:line without editing code or recompiling, and returns a snapshot of the locals, parameters, and instance fields at that exact frame. Use for bug investigation, PlayMode/E2E verification, checking variable values at a specific frame, or confirming that a code path executed.
uloop-screenshot
Capture Unity Editor windows or Game View rendering as PNG. Use for visual checks, debugging, documentation, or annotated UI element coordinates.
uloop-simulate-keyboard
Simulate keyboard input in PlayMode through Unity Input System. Use for key presses, holds (via Press --duration or KeyDown/KeyUp), releases, and game controls such as WASD or Space. Requires the Input System package (com.unity.inputsystem).