awesome-gamedev-agent-skills is a collection of 73 instruction files that give AI coding agents specialized guidance for game development with engines and frameworks such as Godot, Unity, Unreal, and Phaser. It helps agents choose relevant engine and task guidance while building games. The catalogue entries are the collection's skills and plugins for agents including Claude Code, Cursor, Codex, and Gemini CLI.
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 gamedev-skills/awesome-gamedev-agent-skills --skill unity-input-systemgit clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skillsWrote 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/gamedev-skills/awesome-gamedev-agent-skills/unity-input-system)<a href="https://agentmods.dev/skills/gamedev-skills/awesome-gamedev-agent-skills/unity-input-system"><img src="https://agentmods.dev/badge/skills/gamedev-skills/awesome-gamedev-agent-skills/unity-input-system/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/gamedev-skills/awesome-gamedev-agent-skills/unity-input-system"><img src="https://agentmods.dev/badge/skills/gamedev-skills/awesome-gamedev-agent-skills/unity-input-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00083 | $0.01916 |
| Opus 5.5 | $0.00033 | $0.00766 |
| Sonnet 5.5 | $0.00017 | $0.00383 |
| Haiku 4.5 | $0.00008 | $0.00192 |
Grade A, and why
unity-input-system 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 2d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Input System (new)
Read input through Unity's Input System package (com.unity.inputsystem 1.x; Unity 6.3 LTS
ships 1.20) — action-based, device-agnostic, rebindable. Targets Unity 6.3 LTS. This is the modern
replacement for the legacy Input.GetAxis/Input.GetKey Input Manager.
When to use
- Use when setting up movement/jump/fire input, defining an
.inputactionsasset with action maps and control schemes, wiring aPlayerInputcomponent, reading aVector2stick/WASD value, or handling gamepad + keyboard + touch from one set of actions. - Use when
Packages/manifest.jsoncontainscom.unity.inputsystemor the project has an*.inputactionsasset.
When not to use: rebindable-control architecture across engines → input-systems
(this skill is the Unity-specific API). Moving the character once you have the input vector
→ unity-physics / unity-csharp-scripting.
Core workflow
- Check Active Input Handling (Project Settings → Player). The package only receives
input when this is
Input System Package (New)orBoth.Bothis required if any oldInput.GetAxiscode remains. - Find or create the
.inputactionsasset. New Unity 6 projects usually already have one assigned as the project-wide actions (Project Settings → Input System Package; the template file isInputSystem_Actions.inputactions) — reuse it rather than adding a second asset. Add an action map (e.g.Gameplay), add actions (Move= Value/Vector2,Jump= Button,Fire= Button), and bind them to controls and composite bindings (WASD = 2D Vector composite). - Choose how to read it:
PlayerInputcomponent (designer-friendly) — drop it on the player, point it at the asset, pick a Behavior (Send Messages / Broadcast / Invoke Unity Events / Invoke C# Events). Best for single/local-coop players.- Project-wide actions in code (
InputSystem.actions.FindAction("Move")) — no asset reference to wire up, and the actions are already enabled. - Direct in code (
InputActionReference/InputActionAsset) — most control; youEnable()actions and read them. Best for systems and tools.
- Enable the actions/maps you read.
PlayerInputenables its default map automatically and project-wide actions start enabled; actions from any other asset must be.Enable()d (and disabled on teardown). - Switch action maps for context (gameplay ↔ UI/menu) instead of guarding every handler.
- Verify with the Input Debugger (Window → Analysis → Input Debugger) to confirm devices and that actions fire.
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.
- 2d ago Changed · +41 lines e8ed83bbdb8e
- 1mo ago First seen · 140 lines · 83 tokens per session scan A e24e667db006
unity-input-system is a skill published in the GitHub repository gamedev-skills/awesome-gamedev-agent-skills (4,867 stars, last pushed 3d ago), licensed Apache-2.0. It adds 83 tokens to every session and 1,916 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-08-30.
Other skills, from other repositories
editor-session-quit
Save and quit an editor that a CLI session started (unity-mcp-cli exec, open --headless). Needs the session lease nonce; an editor the user opened is never closed. Used by unity-mcp-cli close.
screenshot-game-view
Capture a screenshot of the Unity Editor's Game View by reading its internal render texture directly. Image size matches the current Game View resolution; the tool corrects Y-flip on DirectX / Metal so the output is always upright. Requires an open Game View window.
dialogue-manager
Use when using the Dialogue Manager addon — .dialogue files with titles, responses, conditions and mutations, runtime balloons, and C# support.
event-bus
Use when implementing decoupled communication between nodes — global EventBus autoload with typed signals.
physics-system
Use when working with physics bodies, collision shapes, raycasting, areas, rigid bodies, ragdolls, soft bodies, Jolt physics, and physics interpolation in Godot 4.3+.
biome-detail-tuning
Configure and tune Unity Terrain detail (grass/flower/fern) placement for MapGenerator biomes using prefabs and noise-driven clustering. Covers the full workflow from prefab selection through noise parameter tuning to external audit verification and performance optimization. Use when: setting up detail for any biome…