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 IdoCohen560/claude-unity-game-studio --skill asset-specgit clone --depth 1 https://github.com/IdoCohen560/claude-unity-game-studioWrote 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/idocohen560/claude-unity-game-studio/asset-spec)<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/asset-spec"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/asset-spec/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/idocohen560/claude-unity-game-studio/asset-spec"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/asset-spec.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.00054 | $0.03048 |
| Opus 5 | $0.00027 | $0.01524 |
| Sonnet 5 | $0.00011 | $0.00610 |
| Haiku 4.5 | $0.00005 | $0.00305 |
Grade A, and why
asset-spec 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 9d 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
91% identical to asset-spec — 106 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
If no argument is provided, check whether design/assets/asset-manifest.md exists:
- If it exists: read it, find the first context (system/level/character) with any asset at status "Needed" but no spec file written yet, and use
AskUserQuestion:- Prompt: "The next unspecced context is [target]. Generate asset specs for it?"
- Options:
[A] Yes — spec [target]/[B] Pick a different target/[C] Stop here
- If no manifest: fail with:
"Usage:
/asset-spec system:<name>— e.g.,/asset-spec system:tower-defenseOr:/asset-spec level:iron-gate-fortress//asset-spec character:frost-wardenRun after your art bible and GDDs are approved."
Phase 0: Parse Arguments
Extract:
- Target type:
system,level, orcharacter - Target name: the name after the colon (normalize to kebab-case)
- Review mode:
--review [full|lean|solo]if present
Mode behavior:
full(default): spawn bothart-directorandtechnical-artistin parallellean: spawnart-directoronly — faster, skips technical constraint passsolo: no agent spawning — main session writes specs from art bible rules alone. Use for simple asset categories or when speed matters more than depth.
Phase 1: Gather Context
Read all source material before asking the user anything.
Required reads:
-
Art bible: Read
design/art/art-bible.md— fail if missing:"No art bible found. Run
/art-biblefirst — asset specs are anchored to the art bible's visual rules and asset standards." Extract: Visual Identity Statement, Color System (semantic colors), Shape Language, Asset Standards (Section 8 — dimensions, formats, polycount budgets, texture resolution tiers). -
Technical preferences: Read
.claude/docs/technical-preferences.md— extract performance budgets and naming conventions.
Source doc reads (by target type):
- system: Read
design/gdd/[target-name].md. Extract the Visual/Audio Requirements section. If it doesn't exist or reads[To be designed]:"The Visual/Audio section of
design/gdd/[target-name].mdis empty. Either run/design-system [target-name]to complete the GDD, or describe the visual needs manually." UseAskUserQuestion:[A] Describe needs manually/[B] Stop — complete the GDD first - level: Read
design/levels/[target-name].md. Extract art requirements, asset list, VFX needs, and the art-director's production concept specs from Step 4. - character: Read
design/narrative/characters/[target-name].mdor searchdesign/narrative/for the character profile. Extract visual description, role, and any specified distinguishing features.
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.
- 9d ago First seen · 265 lines · 54 tokens per session scan A b537ae2bc14b
asset-spec is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (18 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 3,048 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to asset-spec, differing in 106 lines, and is treated as a copy.
Other skills, from other repositories
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…
memory-loop-setup
Bootstrap the memory loop into any repo or Obsidian vault. Triggers: (1) "set up the memory loop / second brain / warm layer here" or "install this structure in another repo/vault", (2) a new project asking "make the AI remember across sessions and surfaces".
extract-y2b-insights
Extract the most controversial or genuinely-novel insights from a YouTube video and output them both as a .txt file and printed in the terminal. Use when the user provides a YouTube URL and wants the key ideas, hot takes, or original thinking — NOT video clips. Optionally cross-checks ideas against the web to judge…
plan-qa
Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA- - .md) that /execute-qa…
review
Phase 5 of 5 — triage-first review orchestrator; dispatches up to 17 domain checks in parallel and compiles one report. Use only when the user asks to run Phase 5 or review a PR, branch, or set of changes — never trigger automatically after writing code.
execute-qa
Executes a QA specification (specs/qa/QA- - .md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact…