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 hatayama/unity-cli-loop --skill skillgit clone --depth 1 https://github.com/hatayama/unity-cli-loopWrote 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/hatayama/unity-cli-loop/skill)<a href="https://agentmods.dev/skills/hatayama/unity-cli-loop/skill"><img src="https://agentmods.dev/badge/skills/hatayama/unity-cli-loop/skill/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/hatayama/unity-cli-loop/skill"><img src="https://agentmods.dev/badge/skills/hatayama/unity-cli-loop/skill.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.00034 | $0.00215 |
| Opus 5.5 | $0.00014 | $0.00086 |
| Sonnet 5.5 | $0.00007 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
uloop-get-project-info 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.
What it actually says
uloop get-project-info
Get detailed Unity project information.
Usage
uloop get-project-info
Parameters
None.
Output
Returns JSON with:
ProjectName: Application product nameCompanyName: Company nameVersion: Application versionUnityVersion: Unity Editor versionPlatform: Current platformDataPath: Assets folder pathIsEditor: Whether running in editorIsPlaying: Whether in play modeDeviceType: Device typeOperatingSystem: OS informationProcessorType: CPU typeSystemMemorySize: RAM size in MBGraphicsDeviceName: GPU name
Notes
This is a sample custom tool demonstrating how to create Unity CLI Loop tools.
What ships with it
1 file 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 Changed · +1 lines 11f8f8bd5591
- 1mo ago First seen · 41 lines · 34 tokens per session scan A fa1aa2a893f1
uloop-get-project-info is a skill published in the GitHub repository hatayama/unity-cli-loop (581 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 215 once invoked, about $0.0001 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
unity-ui
A Unity user-interface development and testing workflow for UI Toolkit and uGUI, Unity's two main UI systems.
unity-shared
Shared rules for working with Unity Editor instances through the Unity command-line relay.
unity-verify
A Unity Editor verification workflow that refreshes the project, waits for compilation, checks errors, and can run tests.
unity-api
A workflow for searching and calling Unity’s public programming interface, or API—the collection of functions exposed by Unity. It uses commands to find available methods and run them, including methods not covered by other tools.
unity-scene
A workflow for building Unity game scenes by placing objects, configuring components, turning objects into Prefabs (reusable object templates), and saving scenes.
unity-asset
A workflow for managing Unity project assets, such as scenes, prefabs, scripts, and data files. It examines dependencies, references, prefabs, and installed packages.