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.
curl -O https://raw.githubusercontent.com/hatayama/unity-cli-loop/main/.agents/skills/uloop-run-tests/SKILL.mdgit 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/uloop-run-tests)<a href="https://agentmods.dev/skills/hatayama/unity-cli-loop/uloop-run-tests"><img src="https://agentmods.dev/badge/skills/hatayama/unity-cli-loop/uloop-run-tests/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/uloop-run-tests"><img src="https://agentmods.dev/badge/skills/hatayama/unity-cli-loop/uloop-run-tests.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.00045 | $0.01394 |
| Opus 5.5 | $0.00018 | $0.00558 |
| Sonnet 5.5 | $0.00009 | $0.00279 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
uloop-run-tests 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 7d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
uloop run-tests
Execute Unity Test Runner. When a test or suite fails or a test ends inconclusive, NUnit XML results with failure messages, stack traces, and inconclusive reasons are automatically saved. Read the XML file at XmlPath for detailed diagnosis.
uloop run-tests automatically compiles pending script changes before running tests. Pass --skip-compile only while validating active hot-reload patches, because the compile clears those patches; otherwise let the default compile surface errors and run against current scripts. --skip-compile skips only the CLI-side compile: script edits saved since the last compile can still be imported during the run; such an import reloads the domain as soon as the run releases its assembly lock, discarding active patches and ending the request. While hot reload holds Auto Refresh (the state an apply leaves), a verified run kept the patches live. Check uloop hot-reload --status after the run instead of assuming either outcome.
Before executing tests, uloop run-tests handles unsaved loaded Scene and Prefab Stage changes according to --unsaved-changes (default save): save writes them first, fail stops if any remain, and discard reloads disk state so tests run against saved files. Untitled scenes cannot be discarded and fail. If the chosen mode cannot proceed, it returns Success: false, keeps TestCount at 0, lists the items in Message, and does not start the Unity Test Runner.
Active pause points are automatically cleared (the underlying code patches are removed as well) before test execution begins. Cleared IDs are reported in the response's ClearedPausePointIds field.
A test run can end by discarding active hot-reload changes: script edits imported during the run are compiled when the test runner releases its assembly-reload lock, and that deferred domain reload wipes the patches even though the tests themselves ran patched. The response's Warning field appears whenever changes were live when the run started and does not say whether they survived; check 'uloop hot-reload --status', then re-apply 'uloop hot-reload' or bake the edits in with 'uloop compile' before the next Play or test run.
NoTestsFound means zero tests matched — not a test failure. Check NoTestsFoundExplanation and Message for asmdef hints. When an unfiltered run finds no tests and the project has no test assembly for the TestMode, ProposedTestAsmdef carries a ready-to-write .asmdef: save Content at AssetPath, move the test scripts under that folder, then compile and rerun.
Status: Inconclusive means no test failed but at least one could not meet an Assume; Success is false, as Unity's batchmode test run also fails for it. InconclusiveTests names them with the assumption's message. A test that cannot run in this environment should call Assert.Ignore so it reports as skipped.
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.
- 7d ago Changed · +15 tokens per session 264950c3294a
- 21d ago Changed feaa1d73810c
- 23d ago Changed · -22 lines 0fc98277ad1c
- 29d ago Changed · -4 lines e39a34a5c4c9
- 1mo ago Changed · +5 lines 05e650cf47d5
- 1mo ago Changed e9415d1adcb9
- 1mo ago Changed f2b8569fdf41
- 1mo ago Changed · +4 lines 94d6c0d3ef44
- 1mo ago Changed · -4 lines c9df7a3e7ea2
- 2mo ago First seen · 72 lines · 30 tokens per session scan A 688fc402b606
uloop-run-tests is a skill published in the GitHub repository hatayama/unity-cli-loop (586 stars, last pushed 2d ago), licensed MIT. It adds 45 tokens to every session and 1,394 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
unity-ui
A Unity user-interface development and testing workflow for UI Toolkit and uGUI, Unity's two main UI systems.
unity-verify
A Unity Editor verification workflow that refreshes the project, waits for compilation, checks errors, and can run tests.
test-designing-guide
Provides test design methodology for Unity projects. Use this skill whenever designing test cases from requirements or specifications, including selecting test techniques, deriving test cases, and formatting them. Even for small features, load this skill to ensure test design rigor.
fix-bug
Diagnoses and fixes bugs using a test-first workflow (reproduce, diagnose, fix). Use this skill whenever the user reports a bug, describes unexpected behavior, or asks to investigate or fix a defect. Even if the user says "something's broken", "this isn't working", "fix this bug", or "why does X happen", load this…
test-writing-guide
Provides guidelines for writing test code for Unity projects. Make sure to use this skill whenever writing, creating, editing, or modifying test code files (files under Tests/). This includes implementing new tests, fixing test failures, adding test cases, or any task that results in test code changes. Even for small…
asp-ft-player-builds
Build and run release players of Aspid.FastTools on macOS in one command - Mac Mono, Mac IL2CPP (Managed Stripping Level Minimal and High) and the iOS Simulator - and check that SerializableType resolves its stored names and that ENABLEPROFILER is off. Covers the "player builds" items of the release checklist. …