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 sonereraslan/local-marketplace --skill unity-subagent-devgit clone --depth 1 https://github.com/sonereraslan/local-marketplaceWrote 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/sonereraslan/local-marketplace/unity-subagent-dev)<a href="https://agentmods.dev/skills/sonereraslan/local-marketplace/unity-subagent-dev"><img src="https://agentmods.dev/badge/skills/sonereraslan/local-marketplace/unity-subagent-dev.svg" alt="Measured on agentmods" 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.00098 | $0.01568 |
| Opus 5 | $0.00049 | $0.00784 |
| Sonnet 5 | $0.00020 | $0.00314 |
| Haiku 4.5 | $0.00010 | $0.00157 |
Grade A, and why
unity-subagent-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 8d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent-Driven Development (Unity)
Execute plan by dispatching a fresh subagent per task, with two-stage review after each: spec compliance first, then Unity code quality.
Core principle: Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration.
Senior Unity principles enforced:
- Architecture consistency over local optimization
- Composition over inheritance (especially for MonoBehaviours)
- Isolate pure C# domain logic from Unity-specific glue code
- Minimize hidden coupling (no implicit scene dependencies)
- Validate runtime behavior, not just compilation
- Avoid premature abstraction, but always leave extension points
When to Use
- Have an implementation plan with mostly independent tasks
- Want to stay in this session (vs. parallel session with
unity-executing-plans) - Want fresh subagent per task (no context pollution) with two-stage review
The Process
- Read plan, extract tasks, restate architectural intent, create task list
- For each task:
a. Dispatch implementer subagent (read and fill
./implementer-prompt.md) b. If implementer asks questions, answer them, then re-dispatch c. Implementer implements, tests, stages files, self-reviews d. Dispatch spec reviewer (read and fill./spec-reviewer-prompt.md) e. If not spec compliant, implementer fixes gaps, re-review f. Dispatch code quality reviewer (read and fill./code-quality-reviewer-prompt.md) g. If not quality approved, implementer fixes issues, re-review h. Mark task complete - After all tasks: dispatch final reviewer for entire implementation
- Invoke
superunity:unity-finishing-branch
Prompt Templates
Before dispatching any subagent, read the corresponding prompt template file and fill in all bracketed placeholders with actual task content.
./implementer-prompt.md— Dispatch implementer subagent./spec-reviewer-prompt.md— Dispatch spec compliance reviewer subagent./code-quality-reviewer-prompt.md— Dispatch code quality reviewer subagent
What ships with it
3 files 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.
- 8d ago First seen · 161 lines · 98 tokens per session scan A 4538dd3b9966
unity-subagent-dev is a skill published in the GitHub repository sonereraslan/local-marketplace (2 stars, last pushed 4mo ago), licensed MIT. It adds 98 tokens to every session and 1,568 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
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).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.