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 agentmods add skills/hatayama/unity-cli-loop/uloop-simulate-mouse-inputnpx skills add hatayama/unity-cli-loop --skill uloop-simulate-mouse-inputgit clone --depth 1 https://github.com/hatayama/unity-cli-loopWhat 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 | $0.00113 | $0.01941 |
| Opus 5 | $0.00056 | $0.00971 |
| Sonnet 5 | $0.00023 | $0.00388 |
| Haiku 4.5 | $0.00011 | $0.00194 |
Grade A, and why
uloop-simulate-mouse-input 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
Simulate mouse input via Input System in Unity PlayMode, or dry-run a Game View coordinate against 3D physics without injecting input.
Workflow
- When checking what a screenshot coordinate would hit in 3D physics before clicking, run
uloop simulate-mouse-input --dry-run --x <x> --y <y>first (EditMode is fine; no Input System required) - Ensure Unity is in PlayMode (use
uloop control-play-mode --action Playif not) before injecting real mouse input - For Click/LongPress: determine the target Game View input position from annotated
SimX/SimY, raycast-gridInputX/InputY, or raw image pixels converted withScreenshotToInputFormula - Execute the needed
uloop simulate-mouse-inputcommands - Inspect the result with the lightest useful evidence: runtime state, logs, or a screenshot
- When this input verifies a state transition, use Pause Point inspection from the section below as the standard frame proof
- Report what happened and which evidence was used
Two rules while verifying:
- Do not touch the physical mouse or keyboard, and keep the OS pointer off the Unity window — real device input mixes into the same
Mouse.currentstate this tool injects. - Read the starting values you will assert against immediately before firing the input; a value measured earlier in the session may have changed.
Tool Reference
uloop simulate-mouse-input --action <action> [options]
uloop simulate-mouse-input --dry-run --x <x> --y <y> [--layer-mask <mask>] [--max-distance <distance>]
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
--action |
enum | Click |
Click - inject button press+release, LongPress - inject button hold for --duration seconds, MoveDelta - inject mouse delta (one-shot), SmoothDelta - inject mouse delta smoothly over --duration seconds, Scroll - inject scroll wheel |
--x |
number | 0 |
Target X position in Game View pixels (origin: top-left). Used by Click, LongPress, and --dry-run. Use AnnotatedElements[].SimX, or raw image pixels converted with ScreenshotToInputFormula. |
--y |
number | 0 |
Target Y position in Game View pixels (origin: top-left). Used by Click, LongPress, and --dry-run. Use AnnotatedElements[].SimY, or raw image pixels converted with ScreenshotToInputFormula. |
--button |
enum | Left |
Mouse button: Left, Right, Middle. Used by Click and LongPress. |
--duration |
number | 0 |
Hold duration for LongPress, or interpolation duration for SmoothDelta (seconds, max 30). For Click, 0 = one-shot tap. |
--delta-x |
number | 0 |
Delta X in pixels for MoveDelta/SmoothDelta. Positive = right. |
--delta-y |
number | 0 |
Delta Y in pixels for MoveDelta/SmoothDelta. Positive = up. |
--scroll-x |
number | 0 |
Horizontal scroll delta for Scroll action. |
--scroll-y |
number | 0 |
Vertical scroll delta for Scroll action. Positive = up, negative = down. Typically 120 per notch. |
--dry-run |
flag | - | Query 3D physics at --x/--y without injecting mouse input. Works in EditMode and without the Input System package. Skips PlayMode / Input System preflight. |
--layer-mask |
number | Unity default raycast layers | Physics layer mask used by the raycast. Effective only with --dry-run. |
--max-distance |
number | 1000 |
Maximum raycast distance in world units. Effective only with --dry-run. |
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.
- yesterday Changed · +2 lines · +69 tokens per session 7cd9ad35eddb
- 2d ago First seen · 129 lines · 44 tokens per session scan A 9fe5c18d2371
uloop-simulate-mouse-input is a skill published in the GitHub repository hatayama/unity-cli-loop (522 stars, last pushed yesterday), licensed MIT. It adds 113 tokens to every session and 1,941 once invoked, about $0.0006 per session on Opus 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
Compile, test, and drive Unity for this repo's C# packages (unity/core, jint, quickjs, clearscript) and the two Unity projects (tests/, kitchen-sink/). Use when a change touches C# under unity/, when Unity test results are needed, when a rendering snapshot has to be checked or regenerated, or when the app has to be…
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…
plan-feature
Orchestrates the test-first implementation planning workflow for feature implementation and spec changes. Use this skill whenever plan mode is active and the task involves implementing or adding a new feature, or changing an existing specification. Even if the user only says "plan this" or "how should we implement…
refine-tests
Reviews existing test code for conformance to the test-designing-guide and test-writing-guide, then applies the refinements. Use this skill when the user wants to review or refine existing test code so it follows the project's test design and writing conventions. Typically invoked as /refine-tests .
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…