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 dyCuong03/unity-agent-team --skill architecturegit clone --depth 1 https://github.com/dyCuong03/unity-agent-teamWrote 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/dycuong03/unity-agent-team/architecture)<a href="https://agentmods.dev/skills/dycuong03/unity-agent-team/architecture"><img src="https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/architecture/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/dycuong03/unity-agent-team/architecture"><img src="https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/architecture.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.00096 | $0.01211 |
| Opus 5.5 | $0.00038 | $0.00484 |
| Sonnet 5.5 | $0.00019 | $0.00242 |
| Haiku 4.5 | $0.00010 | $0.00121 |
Grade A, and why
unity-architecture 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 11d 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
89% identical to unity-architecture — 22 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Architecture Advisor
Use this before generating lots of gameplay scripts or when the user asks for a cleaner architecture.
Workflow
- Identify scope: prototype, small game, or long-lived project.
- Define the core loop and the minimum runtime systems needed.
- Recommend the smallest architecture that fits the scope.
- Separate:
- scene/bootstrap layer
- gameplay/domain logic
- data/config assets
- view/presentation layer
- Call out what should stay simple now vs what is worth abstracting.
Output Format
When using this skill, structure the advice as:
- Project tier: prototype / small-game / long-lived
- Recommended modules: 3-7 modules with one-line responsibilities
- Scene/bootstrap plan: where composition and initialization happen
- Data ownership: what belongs in scene objects, ScriptableObjects, or pure C# classes
- Communication rules: direct refs, interfaces, events, or commands
- Performance risks: only the hot paths that matter
- Do now / skip now: avoid over-engineering
Default Guidance
- Prefer thin
MonoBehaviourscripts as composition bridges. - Put reusable gameplay rules in plain C# classes when possible.
- Use
ScriptableObjectfor authored config and shared static data, not as a default dump for runtime state. - Keep dependencies explicit. Avoid hidden global state unless the project size clearly justifies a small service layer.
- Favor simple module boundaries over framework-heavy architecture.
Explicit Execution Order and Entry Guards
Most "random" gameplay bugs trace back to two silent assumptions: that scripts run in a predictable order, and that Update runs only when its data is ready. Neither is true unless you make them so.
Make startup order explicit
Do not rely on Script Execution Order panels or accidental Awake ordering. Prefer these patterns in order of preference:
- One Bootstrap script as the single entry point. It owns the initialization sequence and calls
sub.Init()on the managers it creates. Only this one script has[DefaultExecutionOrder(-10000)]. - Pull, don't push: a subscriber that needs data calls
source.GetValue()on demand or subscribes to an event. A publisher that pushes into others during its ownAwakecreates hidden order dependencies. - Reserve
[DefaultExecutionOrder(n)]for load-bearing singletons only (Bootstrap, InputRouter, SceneController). If more than 3-4 scripts need it, the architecture is wrong, not the ordering.
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.
- 11d ago First seen · 94 lines · 96 tokens per session scan A 5660226fa5a8
unity-architecture is a skill published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 1,211 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to unity-architecture, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
playtest-report
Structured playtest report template, or turn existing playtest notes into structured feedback.
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
motion
Reconstruct a skeleton from calibrated mesh projections and sequential VLM joint annotations, then fit joints and skin weights. Generate motion from joint-position trajectories, rhythm and contact constraints through IK; refine bone orientation against the action, then export, retarget and validate on the target mesh.