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 IdoCohen560/claude-unity-game-studio --skill unity-state-machinesgit clone --depth 1 https://github.com/IdoCohen560/claude-unity-game-studioWrote 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/idocohen560/claude-unity-game-studio/unity-state-machines)<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/unity-state-machines"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/unity-state-machines/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/idocohen560/claude-unity-game-studio/unity-state-machines"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/unity-state-machines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.02797 |
| Opus 5 | $0.00031 | $0.01399 |
| Sonnet 5 | $0.00012 | $0.00559 |
| Haiku 4.5 | $0.00006 | $0.00280 |
Grade A, and why
unity-state-machines 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 6d 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.
This is a copy
100% identical to unity-state-machines — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State & Behavior Systems -- Decision Patterns
Prerequisite skills:
unity-game-architecture(MonoBehaviour vs plain C#, component composition),unity-animation(Animator FSM, StateMachineBehaviour),unity-scripting(MonoBehaviour lifecycle)
These patterns address the most common state management failure: Claude writes ad-hoc if/else chains or giant switch statements with no structure, making state logic unmaintainable beyond 3-4 states.
PATTERN: State System Selection
WHEN: Implementing AI behavior, game flow, character states, or UI navigation
DECISION:
- Animator FSM -- States are tied to animations. Character locomotion, attack combos, death animations. Designer-friendly visual graph. See
unity-animationfor full coverage -- do not build a code FSM just to drive animations. - Code FSM (enum or class-based) -- Game flow (MainMenu/Playing/Paused/GameOver), ability systems, turn phases. Fully testable, no Animator overhead. Use when states have complex logic, not just animation swaps.
- Hierarchical FSM (HFSM) -- States within states. Combat contains {Melee, Ranged, Blocking}. When flat FSM has too many transitions between related states.
- Behavior Tree (BT) -- Complex AI with prioritization, interruptible sequences, parallel behaviors. When FSM has >8-10 states and transition explosion makes the graph unreadable.
- Stack-Based (Pushdown) -- UI screens, pause menus, modal dialogs. States push/pop, previous state is preserved and resumed.
How many states? What kind of transitions?
|
+-- 2-3 states, simple toggling?
| --> if/else or bool flags (don't over-engineer)
|
+-- 4-8 states, clear transitions?
| --> Code FSM (enum or IState)
|
+-- States group naturally into clusters?
| --> HFSM (Locomotion > {Idle,Walk,Run}, Combat > {Melee,Ranged})
|
+-- AI with priorities, interrupts, parallel tasks?
| --> Behavior Tree
|
+-- Need to return to previous state (back button, unpause)?
| --> Stack-Based State Machine
|
+-- States tied to animations?
--> Animator FSM (use unity-animation skill)
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.
- 6d ago First seen · 320 lines · 62 tokens per session scan A 19fd60653296
unity-state-machines is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (18 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 2,797 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to unity-state-machines, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…
memory-loop-setup
Bootstrap the memory loop into any repo or Obsidian vault. Triggers: (1) "set up the memory loop / second brain / warm layer here" or "install this structure in another repo/vault", (2) a new project asking "make the AI remember across sessions and surfaces".
discord-intent-application
Helps write the justification text for Discord Developer Portal privileged intent applications (Message Content, Server Members, Presence) for a specific bot. Takes a plain-text description of the bot's functionality and/or an uploaded/local codebase, screens the bot's features against Discord's known rejection…
plan-qa
Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA- - .md) that /execute-qa…
review
Phase 5 of 5 — triage-first review orchestrator; dispatches up to 17 domain checks in parallel and compiles one report. Use only when the user asks to run Phase 5 or review a PR, branch, or set of changes — never trigger automatically after writing code.
execute-qa
Executes a QA specification (specs/qa/QA- - .md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact…