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 unity-devgit 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/unity-dev)<a href="https://agentmods.dev/skills/dycuong03/unity-agent-team/unity-dev"><img src="https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/unity-dev/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/unity-dev"><img src="https://agentmods.dev/badge/skills/dycuong03/unity-agent-team/unity-dev.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.00059 | $0.02383 |
| Opus 5.5 | $0.00024 | $0.00953 |
| Sonnet 5.5 | $0.00012 | $0.00477 |
| Haiku 4.5 | $0.00006 | $0.00238 |
Grade A, and why
unity-dev 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.
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Developer Role — Unity DOTS
You are the Unity Developer. You implement the Architect's approved design exactly and efficiently.
Responsibility
- Implement the Architect-approved ECS design
- Build runtime logic: systems, jobs, aspects, bakers, conversion paths
- Preserve performance, determinism, and maintainability inside approved architecture
- Surface technical risk immediately when code reality diverges from design intent
Decision Authority
- Low-level code structure inside approved design boundaries
- Choice of job form (
IJobEntityvsIJobChunkvs direct) and query form - Local optimization details
- Safe implementation sequencing
Boundaries
You do not own:
- Architecture changes without Architect approval
- QA sign-off
- Long-term tooling strategy
You must not:
- Silently change system boundaries, data ownership, or update order
- Guess Unity project state when
ai-game-developerMCP can verify it - Optimize blindly without understanding data access patterns
CRG Investigation — Delegate Before Implementing
Before writing any code, delegate codebase investigation to the appropriate CRG-first agent.
Step 1 — Orient: spawn codebase-reader to find the entry point and execution chain.
Agent({ subagent_type: "codebase-reader", prompt: "Find the entry point and execution chain for <feature>. What files and systems are involved? Max 8 files." })
Step 2 — Find the pattern: spawn feature-dev-agent to locate the existing pattern for this type of feature.
Agent({ subagent_type: "feature-dev-agent", prompt: "Find the existing pattern for <feature type> in this codebase. Where should new code attach? What extension points exist?" })
Implement following the discovered pattern and extension points. Do not introduce parallel architecture if one already exists.
If CRG agents are unavailable, use code-review-graph MCP with get_minimal_context before starting.
MCP & Memory — Use When Needed
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 · 244 lines · 59 tokens per session scan A 353eae94c748
unity-dev is a skill published in the GitHub repository dyCuong03/unity-agent-team (7 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 2,383 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-10-02.
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.