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-simulate-keyboard/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-simulate-keyboard)<a href="https://agentmods.dev/skills/hatayama/unity-cli-loop/uloop-simulate-keyboard"><img src="https://agentmods.dev/badge/skills/hatayama/unity-cli-loop/uloop-simulate-keyboard/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-simulate-keyboard"><img src="https://agentmods.dev/badge/skills/hatayama/unity-cli-loop/uloop-simulate-keyboard.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.00062 | $0.01802 |
| Opus 5.5 | $0.00025 | $0.00721 |
| Sonnet 5.5 | $0.00012 | $0.00360 |
| Haiku 4.5 | $0.00006 | $0.00180 |
Grade A, and why
uloop-simulate-keyboard 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task
Simulate keyboard input on Unity PlayMode.
Workflow
- Ensure Unity is in PlayMode (use
uloop control-play-mode --action Playif not) - Execute the needed
uloop simulate-keyboardcommands - Inspect the result with the lightest useful evidence: runtime state, logs, or a screenshot
- If exact-frame proof would reduce uncertainty, treat Pause Point inspection as an optional follow-up using the section below
- Report what happened and which evidence was used
Tool Reference
uloop simulate-keyboard --action <Press|KeyDown|KeyUp> --key <key> [options]
uloop simulate-keyboard --action ReleaseAll
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
--action |
enum | Press |
Press - one-shot key tap (Down then Up), KeyDown - hold key down, KeyUp - release held key, ReleaseAll - force-release every tracked and device-pressed key (allowed while PlayMode is paused; use after a pause-point interruption leaves key state inconsistent) |
--key |
string | (required except ReleaseAll) |
Key name matching Input System Key enum (e.g. W, Space, LeftShift, A, Enter). Case-insensitive. Digit keys use Digit0-Digit9 or Numpad0-Numpad9, not bare 0-9. Not used by ReleaseAll. |
--duration |
number | 0 |
Hold duration in seconds for Press action (0 = one-shot tap, max 30). Ignored by KeyDown/KeyUp/ReleaseAll. |
Actions
| Action | Behavior | Use Case |
|---|---|---|
Press |
KeyDown → wait → KeyUp | One-shot tap (jump, use item) |
KeyDown |
KeyDown only (held until KeyUp) | Start continuous movement, hold sprint |
KeyUp |
KeyUp only (release held key) | Stop movement, release sprint |
ReleaseAll |
Injects a release for every tracked and device-pressed key and resets the hold tracker; confirm the device via ReleasedKeyStates |
Recover a clean keyboard state after a pause-point interruption |
There is no separate hold action: to hold a key, use Press --duration <seconds> (fixed-time hold) or KeyDown followed later by KeyUp (open-ended hold).
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 8a70e9524f54
- 1mo ago Changed 784183dd8612
- 1mo ago Changed · +15 lines · +23 tokens per session cf91db1335af
- 2mo ago First seen · 88 lines · 39 tokens per session scan A 5eff0ce277cc
uloop-simulate-keyboard is a skill published in the GitHub repository hatayama/unity-cli-loop (586 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 1,802 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-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-scene
A workflow for building Unity game scenes by placing objects, configuring components, turning objects into Prefabs (reusable object templates), and saving scenes.
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-debug
A workflow for investigating runtime errors in the Unity game-development editor, including null references and console messages.