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 agentmods add skills/krogh-jacobsen/unity-code-style-guide/unity-guide-auditnpx skills add krogh-jacobsen/unity-code-style-guide --skill unity-guide-auditgit clone --depth 1 https://github.com/krogh-jacobsen/unity-code-style-guideWrote 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/krogh-jacobsen/unity-code-style-guide/unity-guide-audit)<a href="https://agentmods.dev/skills/krogh-jacobsen/unity-code-style-guide/unity-guide-audit"><img src="https://agentmods.dev/badge/skills/krogh-jacobsen/unity-code-style-guide/unity-guide-audit.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 | $0.00105 | $0.03624 |
| Opus 5 | $0.00053 | $0.01812 |
| Sonnet 5 | $0.00021 | $0.00725 |
| Haiku 4.5 | $0.00011 | $0.00362 |
Grade A, and why
unity-guide-audit 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 4d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Guide Audit
Check a Unity project against the conventions in this repository and report violations with file, line, and the specific rule broken.
This is a conformance check, not a general code review. If the user wants generic Unity pitfall
detection, the unity-project-review skill covers that. This skill answers a narrower question:
does this project follow the documented conventions in UnityStyleGuide.md and
UnityReferenceGuides/?
Before starting
- Locate the guides. Look for
UnityStyleGuide.md,AGENTS.md, orUnityReferenceGuides/in the project root, a parent directory, or a sibling checkout. If none exist, ask the user where they are — do not audit against remembered defaults. - Know which guides exist.
UnityReferenceGuides/currently holds: Performance, Assets & Memory, Design Patterns, Scenes & Lifecycle, UI Toolkit, uGUI, Input System, Animation, Audio, Assembly Definitions, Testing, Editor Tooling, Debugging. Cite the specific one in every finding. - Read the tech stack.
UnityCustomInstructions/UnityTechStack.mdsays which input, UI, and render systems are in use. A uGUI finding is noise in a UI Toolkit project. - Confirm the scope with the user: whole project, one folder, or changes on the current branch.
- Establish the naming convention from the guide, not from memory. The prefixes (
m_/k_/s_) and their casing are configurable preferences. Read them out of the guide before flagging anything.
Phase 1 — Static analysis (always runs)
Needs no Unity Editor. Works in CI. Scan .cs, .uxml, .uss, .asmdef, and
ProjectSettings/*.asset.
Skip Library/, Temp/, obj/, Build/, and any Packages/ cache. Do not report findings inside
third-party plugin folders unless the user asks.
Asset integrity (check these first)
These detect damage, not drift. A finding here is a corrupted project, not a style opinion, so it outranks everything below it.
| Check | How |
|---|---|
| Duplicate GUIDs | Parse guid: from every .meta; any GUID appearing twice is a corrupted project — references resolve non-deterministically |
Orphaned .meta |
A .meta with no matching asset beside it |
Missing .meta |
An asset under Assets/ with no .meta (excluding ignored folders) |
Malformed .meta |
Missing guid:, or a GUID that isn't 32 hex characters |
| Unsafe field rename | In a diff: a serialized field renamed with no [FormerlySerializedAs] on it |
| Enum renumbering | In a diff: members of a serialized enum reordered or given new explicit values |
| Unpaired asset editing | AssetDatabase.StartAssetEditing() without StopAssetEditing() in a finally |
| Committed generated data | Library/, Temp/, obj/, Logs/, UserSettings/ tracked in git |
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.
- 4d ago First seen · 276 lines · 105 tokens per session scan A b7b16ef8712b
unity-guide-audit is a skill published in the GitHub repository krogh-jacobsen/unity-code-style-guide (20 stars, last pushed 6d ago), licensed MIT. It adds 105 tokens to every session and 3,624 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-30.
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.
assets-prefab-save
Save the currently opened prefab edit stage back to its prefab asset without exiting the stage. Pair with 'assets-prefab-open' to enter the edit mode first.
mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
influence-psychology
Apply the seven principles of ethical persuasion (reciprocity, commitment, social proof, authority, liking, scarcity, unity) to product design, copy, and sales. Use when the user mentions "social proof", "persuasive copy", "why users dont convert", "ethical persuasion", "reciprocity", "scarcity tactics", "commitment…
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
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.