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 bullish0x/GameStudio --skill asset-specgit clone --depth 1 https://github.com/bullish0x/GameStudioWrote 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/bullish0x/gamestudio/asset-spec)<a href="https://agentmods.dev/skills/bullish0x/gamestudio/asset-spec"><img src="https://agentmods.dev/badge/skills/bullish0x/gamestudio/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/bullish0x/gamestudio/asset-spec"><img src="https://agentmods.dev/badge/skills/bullish0x/gamestudio/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.03896 |
| Opus 5 | $0.00027 | $0.01948 |
| Sonnet 5 | $0.00011 | $0.00779 |
| Haiku 4.5 | $0.00005 | $0.00390 |
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 7d 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
100% identical to asset-spec — 3 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 — 352 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/entity-inventory.md exists:
- If it exists: read it, find the first entity or screen with status "Needed" but no spec file yet, and use
AskUserQuestion:- Prompt: "The next unspecced item is [name]. Generate specs for it?"
- Options:
[A] Yes — spec [name]/[B] Pick a different item/[C] Stop here
- If no entity inventory: check
design/assets/asset-manifest.md. If manifest exists, same flow above but reading from manifest. - If neither exists: start the Entity & Screen Inventory flow (Phase 0b below) rather than failing.
Phase 0b: Entity & Screen Inventory (runs when no arguments and no existing inventory)
This flow produces design/assets/entity-inventory.md — the master list of everything
the game needs visually. Run once before asset spec work begins.
Step 1 — Gather from docs
Read all available source material in parallel:
design/gdd/systems-index.md— extract every system listed- All GDDs in
design/gdd/— extract: Visual/Audio Requirements sections, UI elements mentioned, VFX events, any named entities (characters, enemies, buildings, items) design/art/art-bible.md— extract: any named visual categories, asset type expectationsdesign/narrative/— scan for any character or world entity documents if they exist (optional — not required)
Step 2 — Build proposed inventory
Organize everything found into categories:
Characters / Protagonists
Enemies / Creatures
Buildings / Structures
Environment / Terrain
Items / Props
VFX / Particles
UI Screens (list each screen by name)
HUD Elements
Audio (SFX, music — descriptions only, no generation prompts)
Other
For each item, note the source doc it was found in.
Step 3 — Present and collaborate
Present the full proposed inventory to the user in conversation. Then use AskUserQuestion:
- Prompt: "I found [N] visual entities and [N] UI screens across your GDDs and art bible. Review the list — what's missing, what's not needed?"
- Options:
[A] Looks good — save this inventory[B] Add items I'll describe[C] Remove items that don't apply[D] Both add and remove — let me edit
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.
- 7d ago First seen · 352 lines · 54 tokens per session scan A 766b3fa54aea
asset-spec is a skill published in the GitHub repository bullish0x/GameStudio (12 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 3,896 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to asset-spec, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
ar-vr-xr
AR/VR/XR development with Unity XR, WebXR, ARKit, ARCore, Meta Quest SDK, and spatial computing. Use when building augmented reality, virtual reality, mixed reality applications, or spatial experiences.
audio-production
Professional audio production for music, podcasts, and sound design. Use when working with audio recording, mixing, mastering, or sound design for any medium.
brand-identity
Brand strategy and identity design for businesses and products. Use when creating brand guidelines, developing visual identity systems, or defining brand positioning.
game-development
Game development with Unity, Unreal Engine, and Godot. Use when building games, implementing game mechanics, physics, AI, or working with game engines.
gamedev-shaders
Use when authoring or debugging a shader, material, VFX, or full-screen post-process in a game engine — Godot 4.x .gdshader, Unity 6 URP/HDRP, Unreal 5.x Materials, effect recipes, shader performance. NOT gameplay or engine-API code (that is godot/unity/unreal), NOT physics (gamedev-physics), NOT build variant…
graphic-design
Professional graphic design principles for digital and print media. Use when creating visual designs, choosing color palettes, typography, layouts, or providing design feedback.