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-code-reviewgit 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-code-review)<a href="https://agentmods.dev/skills/sonereraslan/local-marketplace/unity-code-review"><img src="https://agentmods.dev/badge/skills/sonereraslan/local-marketplace/unity-code-review/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/sonereraslan/local-marketplace/unity-code-review"><img src="https://agentmods.dev/badge/skills/sonereraslan/local-marketplace/unity-code-review.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.00107 | $0.02089 |
| Opus 5 | $0.00053 | $0.01045 |
| Sonnet 5 | $0.00021 | $0.00418 |
| Haiku 4.5 | $0.00011 | $0.00209 |
Grade A, and why
unity-code-review 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review (Unity)
Overview
Review early, review often. Verify before implementing.
Part 1: Requesting Code Review
When to Request
Mandatory:
- After each task in subagent-driven development (
superunity:unity-subagent-dev) - After completing a major feature
- Before merge to main
Valuable but optional:
- When stuck (fresh perspective often unblocks)
- Before refactoring (baseline understanding of current state)
- After fixing a complex bug
How to Request
1. Get git SHAs:
BASE_SHA=$(git rev-parse origin/main) # or the SHA before task started
HEAD_SHA=$(git rev-parse HEAD)
2. Dispatch a code-reviewer subagent:
Dispatch using the Task tool with subagent_type: general-purpose, using the template at ./unity-code-reviewer-prompt.md. Read the template file and fill in all placeholders before dispatching.
Placeholders:
{WHAT_WAS_IMPLEMENTED}— what you just built (one paragraph){PLAN_OR_REQUIREMENTS}— plan file path or inline task spec{BASE_SHA}— commit before the task{HEAD_SHA}— current HEAD{DESCRIPTION}— brief summary (files changed, test count)
3. Act on feedback:
- Fix Critical issues immediately — do not proceed
- Fix Important issues before moving to the next task
- Note Minor issues — fix opportunistically or in a cleanup pass
- Push back with technical reasoning if feedback is wrong
Example
[Completed Task 3: InventoryManager with EditMode tests]
BASE_SHA=$(git log --oneline | grep "Task 2" | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)
[Dispatch unity-code-reviewer subagent]
WHAT_WAS_IMPLEMENTED: Pure C# InventoryManager with add/remove/query,
driven by ItemData ScriptableObject, events for UI binding
PLAN_OR_REQUIREMENTS: Task 3 from docs/plans/2026-02-22-inventory.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
DESCRIPTION: 3 files added, 5 EditMode tests, all passing
[Subagent returns]:
Important: ItemData ScriptableObject has a scene object reference in _defaultContainer
Minor: InventoryManager event naming inconsistent with project conventions
Assessment: Fix Important issue before proceeding
[Fix ScriptableObject reference — scene refs in SOs cause serialization bugs after domain reload]
[Continue to Task 4]
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.
- 8d ago First seen · 236 lines · 107 tokens per session scan A d7b0c79dcebf
unity-code-review is a skill published in the GitHub repository sonereraslan/local-marketplace (2 stars, last pushed 4mo ago), licensed MIT. It adds 107 tokens to every session and 2,089 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
godot-code-review
Use when reviewing GDScript or C# Godot code — checklist of best practices, common anti-patterns, and Godot-specific pitfalls.
animation-review
Reviews Godot Animation implementation for known pitfalls. Triggers AFTER implementation, when code involves AnimationPlayer, AnimationTree, AnimatedSprite2D, SpriteFrames, AnimationNodeStateMachine, BlendSpace, OneShot, callbackmodeprocess, or animation playback control (play/travel/start). Do NOT use this skill for…
tilemap-review
Reviews Godot TileMap implementation for known pitfalls. Triggers AFTER implementation, when code involves TileMapLayer, TileSet, TileSetAtlasSource, TileSetScenesCollectionSource, terrain painting, setcell, erasecell, getcelltiledata, collision polygons on tiles, or NavigationRegion2D with tile-based navigation. Do…
hz-unity-code-review
Reviews Unity code targeting Meta Quest and Horizon OS for performance issues, rendering best practices, and common VR pitfalls. Use during code review or when diagnosing Quest performance problems in Unity projects.
unity-reviewer
Use when reviewing Unity C# code changes — checks for runtime-breaking bugs, performance anti-patterns, and maintainability issues. Provides severity-tiered review organized as Critical, Performance, and Style.
design-lenses
Structured game-design critique: review a game through Schell's design lenses, Wright's systems-and-emergence lenses, and the MDA framework, producing severity-ranked findings with concrete fixes. Use when the user asks 'is my game fun?', 'review my game design', 'why is it boring?', 'critique this game', 'what's…