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 skills add Jason-hub-star/unityctl --skill unityctl-workflowsgit clone --depth 1 https://github.com/Jason-hub-star/unityctlWrote 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/jason-hub-star/unityctl/unityctl-workflows)<a href="https://agentmods.dev/skills/jason-hub-star/unityctl/unityctl-workflows"><img src="https://agentmods.dev/badge/skills/jason-hub-star/unityctl/unityctl-workflows/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/jason-hub-star/unityctl/unityctl-workflows"><img src="https://agentmods.dev/badge/skills/jason-hub-star/unityctl/unityctl-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00079 | $0.00903 |
| Opus 5.5 | $0.00032 | $0.00361 |
| Sonnet 5.5 | $0.00016 | $0.00181 |
| Haiku 4.5 | $0.00008 | $0.00090 |
Grade A, and why
unityctl-workflows 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
unityctl Workflows
Use unityctl as the execution and evidence layer. Keep source-code edits in normal filesystem tools; use unityctl for Unity-owned state and live Editor operations.
Establish the target
- Resolve the Unity project root containing
Assets/,Packages/, andProjectSettings/. - Pass
--projectexplicitly on every project-scoped command. Discovery commands such aseditor currentandeditor instancesare global and do not accept it. - Check the installed CLI and project:
unityctl --version
unityctl doctor --project "$P" --json
- If the bridge is missing, install the bundled bridge, then open Unity and wait for stability:
unityctl init --project "$P"
unityctl await-ready --project "$P" --timeout 300 --json
Do not run init again when doctor reports a healthy matching bridge.
Discover, do not guess
Use the live command surface instead of memorizing flags:
unityctl tools --json
unityctl <command> --help
tools --json returns a top-level array. Use names returned by it; the machine
command catalog uses hyphenated names while the CLI may expose grouped verbs.
unityctl tools --json | jq '.[].name'
Run the closed loop
- Read the current state, including
scene hierarchy --summary. - If any affected scene is already dirty, stop before writing. Ask whether to save the existing work or let the user revert it; do not mix ownership.
- Compare
editor current --jsonwith the intended project. Before writes, select the intended target explicitly when they differ:
unityctl editor current --json
unityctl editor select --project "$P" --json
- Make the smallest Unity-owned change.
- Read back the exact changed field or object.
- Save the affected scene or asset.
- Run the narrowest relevant check.
- Produce artifact evidence for visual or multi-step work.
Prefer stable globalObjectId values after saving a scene. Name targeting is acceptable for initial creation but is ambiguous once duplicates exist.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 96 lines · 79 tokens per session scan A f2a6916ebd86
unityctl-workflows is a skill published in the GitHub repository Jason-hub-star/unityctl (19 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 903 once invoked, about $0.0003 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
gamedev-multiplayer
Use when adding multiplayer or netcode to a game — client-server vs P2P, server authority and anti-cheat, state replication vs RPCs, prediction and reconciliation, lag compensation, plus Godot 4 / Unity NGO / Unreal wiring. NOT single-player gameplay (that is godot, unity, unreal), NOT matchmaking or server hosting…
gamedev-pathing
Use when making NPCs, enemies, or units navigate a level — grid vs waypoint vs navmesh, A/JPS, navmesh baking and agent radius, off-mesh links, steering, RVO crowd avoidance, and flow fields in Godot 4.x, Unity, Unreal. NOT collision response or character controllers (that is gamedev-physics), NOT aggro or difficulty…
csharp-dotnet
Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…
gamedev-physics
Use when working with a game engine's physics — rigid bodies, colliders, collision layers and masks, character controllers, joints, forces versus impulses, raycasts and shapecasts, or when a simulation is unstable (tunnelling, jitter, missed overlaps). Covers the Godot, Unity and Unreal equivalents. NOT rendering or…
gamedev-shaders
Use when authoring or debugging a shader, material, VFX, or full-screen post-process in a game engine — Godot 4.x .gdshader, Unity 6 URP/HDRP, Unreal 5.x Materials, effect recipes, shader performance. NOT gameplay or engine-API code (that is godot/unity/unreal), NOT physics (gamedev-physics), NOT build variant…
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…