unity-cli-loop: Skill for Claude Code

.agents/skills/uloop-status/SKILL.md

uloop-status is a skill for Claude Code, Codex from hatayama/unity-cli-loop. It costs 70 tokens per session (869 once invoked), scanned A, original, MIT.

A read-only status check for whether a Unity Editor project can accept a uloop command. Unity is a game-development editor, and the check reports conditions such as compiling, importing assets, being busy, or not running.

In plain words
What is it for?
Use it before sending a uloop command to find out whether the project is ready, unavailable, or still processing work.
Why use it?
It prevents commands from being sent while Unity is starting, blocked, compiling, or otherwise unable to handle them safely.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is hatayama/unity-cli-loop's own configuration. It tells Claude Code and Codex how to work on unity-cli-loop itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything unity-cli-loop configures →

Reuse

Borrowing it

Nothing to install: this file belongs to hatayama/unity-cli-loop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hatayama/unity-cli-loop/main/.agents/skills/uloop-status/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/hatayama/unity-cli-loop

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for uloop-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/hatayama/unity-cli-loop/uloop-status/github.svg)](https://agentmods.dev/skills/hatayama/unity-cli-loop/uloop-status)
Your own site
<a href="https://agentmods.dev/skills/hatayama/unity-cli-loop/uloop-status"><img src="https://agentmods.dev/badge/skills/hatayama/unity-cli-loop/uloop-status/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.

agentmods 80×15 button for uloop-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/hatayama/unity-cli-loop/uloop-status"><img src="https://agentmods.dev/badge/skills/hatayama/unity-cli-loop/uloop-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 869 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.00869
Opus 5.5 $0.00028 $0.00348
Sonnet 5.5 $0.00014 $0.00174
Haiku 4.5 $0.00007 $0.00087

Measured yesterday against content hash 0c15ccf73fd8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

uloop-status 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.

.agents/skills/uloop-status/SKILL.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

uloop status

Report whether the Unity Editor for this project can take a uloop command now, without changing anything.

Usage

uloop status
uloop status --project-path <path>

States

The states are checked in this order, and the first one that matches is reported.

State Meaning Exit code
Busy Unity answered, and a uloop command is running and holds the command slot 1
Starting Unity answered but has not recorded its play and compile state yet 1
MainThreadBlocked Unity answered, but its main thread has not run for 5 seconds or more, even when asked again after being woken 1
Compiling Unity answered and is compiling scripts 1
ImportingAssets Unity answered and is importing assets 1
Ready Unity answered and none of the above applies 0
NotResponding Connected to Unity, but it did not answer within 5 seconds 1
ServerUnavailable The uloop server refused or dropped the connection, and Unity is running for this project 1
NotRunning The uloop server refused or dropped the connection, and no Unity Editor is running for this project 1
Unreachable The uloop server refused or dropped the connection, and the Unity process list could not be read 1

Some failures are errors, not states: the operating system refusing the connection (as a sandbox does), an error answered by Unity (such as a package too old to support uloop status), an unreadable answer, or an unknown option. These print an error to stderr, nothing to stdout, and exit 1.

Output

Returns JSON with:

  • State: one of the states above
  • Ready: true only for Ready
  • Message: what the state means for this Editor
  • NextActions: what to do next; an empty array for Ready
  • RunningToolName, RunningToolElapsedSeconds, RunningToolPhase (Executing or WaitingForMainThread): the running command; Busy only
  • IsPlaying, IsPaused, IsCompiling, IsUpdating: Unity's play and compile state; only when Unity answered and has recorded that state
  • SecondsSinceLastMainThreadTick: seconds since Unity's main thread last ran; only when Unity answered
  • UnityProcessRunning: whether Unity is running for this project; ServerUnavailable and NotRunning only
  • ConnectionError: the connection error as reported; NotResponding, ServerUnavailable, NotRunning, and Unreachable only

Read the full file on GitHub · 60 lines

Files

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.

Changes

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.

  1. yesterday Changed · +29 tokens per session 0c15ccf73fd8
  2. 15d ago Changed · +1 lines 147afa3bda2e
  3. 23d ago First seen · 59 lines · 41 tokens per session scan A bf833d71b0e2

Subscribe to this mod's changes

uloop-status is a skill published in the GitHub repository hatayama/unity-cli-loop (586 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 869 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-10-06.