Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bigdra50/unity-clinpx agentmods add skills/bigdra50/unity-cli/unity-sceneWrote 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/skills/bigdra50/unity-cli/unity-scene)<a href="https://agentmods.dev/skills/bigdra50/unity-cli/unity-scene"><img src="https://agentmods.dev/badge/skills/bigdra50/unity-cli/unity-scene/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/skills/bigdra50/unity-cli/unity-scene"><img src="https://agentmods.dev/badge/skills/bigdra50/unity-cli/unity-scene.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.00061 | $0.00782 |
| Opus 5.5 | $0.00024 | $0.00313 |
| Sonnet 5.5 | $0.00012 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
unity-scene 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
unity-scene
PREREQUISITE:
../unity-shared/SKILL.md(Relay Server 経由で Unity Editor が起動/アクティブであること)skill 経由のコマンドは必ず
-i <instance>を付ける (unity-shared #インスタンス指定)。
ワークフロー
1. 現状把握 u -i <instance> scene active / u -i <instance> scene hierarchy
2. オブジェクト u -i <instance> gameobject create / find / modify / delete
3. コンポーネント u -i <instance> component add / modify / inspect / list
4. Prefab化 u -i <instance> asset prefab <path> --target <name>
5. シーン保存 u -i <instance> scene save
コマンドリファレンス
Scene
u -i <instance> scene active # アクティブシーン情報
u -i <instance> scene hierarchy --depth 2 # 階層表示
u -i <instance> scene load --path "Assets/..." # シーン読み込み
u -i <instance> scene save # 保存
GameObject
u -i <instance> gameobject create "Player" # 空オブジェクト
u -i <instance> gameobject create "Cube" --primitive Cube # プリミティブ
u -i <instance> gameobject find --name "Player" # 検索
u -i <instance> gameobject modify -n "Player" --position 0,1,0 # Transform変更
u -i <instance> gameobject delete -n "Player" # 削除
Component
u -i <instance> component list -t "Player" # 一覧
u -i <instance> component inspect -t "Player" -T Rigidbody # 詳細
u -i <instance> component add -t "Player" -T Rigidbody # 追加
u -i <instance> component modify -t "Player" -T Rigidbody --prop mass --value 2 # 変更
u -i <instance> component remove -t "Player" -T Rigidbody # 削除
Asset
u -i <instance> asset prefab "Assets/Prefabs/Player.prefab" --target "Player" # Prefab化
u -i <instance> asset info "Assets/Prefabs/Player.prefab" # 情報
CLI 非対応操作
unity-shared のフォールバック順に従う:
u -i <instance> api schema --type <Type>で対応メソッドを検索u -i <instance> api callで実行- .meta インポート設定等は YAML 直接編集
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 · 76 lines · 61 tokens per session scan A 97db36bdb852
unity-scene is a skill published in the GitHub repository bigdra50/unity-cli (39 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 782 once invoked, about $0.0002 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-30.
Other skills, from other repositories
uloop-get-project-info
Get Unity project information via uloop CLI. Use when you need to check project settings, Unity version, platform, or other project metadata.
aibridge-prefab-patch
Unity Prefab asset patch workflow for AIBridge. Use when modifying complex prefab assets with prefab patch operations, child or component creation, SerializedProperty writes, array edits, internal GameObject/component references, dry-run validation, or when deciding between prefab patch, inspector setproperty, scene…
aibridge
Unity Editor and Player Runtime CLI integration for AIBridge. Use for harness snapshot reads, Unity compile/logs/assets/scenes/prefabs/Inspector, screenshots/GIFs, Play Mode input, Runtime Player targets, focus/menu/game view, or AIBridgeCLI syntax. Route batch/multi, complex prefab patching, and direct UnityYAML…
aibridge-code-index
Optional read-only AIBridge Code Index lightweight lookup for Unity C# declaration names. Use only when Root Rule declares Code Index enabled and this Skill is installed. Map declaration names to files or positions. Do not use for references, callers, implementations, derived types, diagnostics, comments, strings, or…
aibridge-development-workflow
A development workflow guide for projects built with Unity, a game and interactive-app engine. It routes coding, asset changes, debugging, reviews, and validation through project-specific rules and checks.
aibridge-workflow-orchestration
AIBridge workflow and multi-agent orchestration guidance. Use when Codex needs to design, review, or execute a multi-agent workflow plan, split Unity work into parallel or pipeline agent roles, define structured workflow artifacts, choose between batch/multi automation and agent orchestration, run adversarial…