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/traftg/opencode-game-studio/design-systemnpx skills add TraftG/opencode-game-studio --skill design-systemgit clone --depth 1 https://github.com/TraftG/opencode-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/traftg/opencode-game-studio/design-system)<a href="https://agentmods.dev/skills/traftg/opencode-game-studio/design-system"><img src="https://agentmods.dev/badge/skills/traftg/opencode-game-studio/design-system.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.00045 | $0.04161 |
| Opus 5 | $0.00023 | $0.02080 |
| Sonnet 5 | $0.00009 | $0.00832 |
| Haiku 4.5 | $0.00005 | $0.00416 |
Grade A, and why
design-system 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- design-system — 98% identical, 2 lines differ
- design-system — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When this skill is invoked:
1. Parse Arguments & Validate
A system name argument is required. If missing, fail with:
"Usage:
/design-system <system-name>— e.g.,/design-system combat-systemRun/map-systemsfirst to create the systems index, then use this skill to write individual system GDDs."
Normalize the system name to kebab-case for the filename (e.g., "combat system"
becomes combat-system).
2. Gather Context (Read Phase)
Read all relevant context before asking the user anything. This is the skill's primary advantage over ad-hoc design — it arrives informed.
2a: Required Reads
- Game concept: Read
design/gdd/game-concept.md— fail if missing:"No game concept found. Run
/brainstormfirst." - Systems index: Read
design/gdd/systems-index.md— fail if missing:"No systems index found. Run
/map-systemsfirst to map your systems." - Target system: Find the system in the index. If not listed, warn:
"[system-name] is not in the systems index. Would you like to add it, or design it as an off-index system?"
2b: Dependency Reads
From the systems index, identify:
- Upstream dependencies: Systems this one depends on. Read their GDDs if they exist (these contain decisions this system must respect).
- Downstream dependents: Systems that depend on this one. Read their GDDs if they exist (these contain expectations this system must satisfy).
For each dependency GDD that exists, extract and hold in context:
- Key interfaces (what data flows between the systems)
- Formulas that reference this system's outputs
- Edge cases that assume this system's behavior
- Tuning knobs that feed into this system
2c: Optional Reads
- Game pillars: Read
design/gdd/game-pillars.mdif it exists - Existing GDD: Read
design/gdd/[system-name].mdif it exists (resume, don't restart from scratch) - Related GDDs: Glob
design/gdd/*.mdand read any that are thematically related (e.g., if designing "status-effects", also read "combat-system" even if it's not a direct dependency)
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.
- 2d ago First seen · 497 lines · 45 tokens per session scan A ad9c1f18cc7e
design-system is a skill published in the GitHub repository TraftG/opencode-game-studio (38 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 4,161 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
professional-game-developer
Universal production game engineering skill — design, build, profile, test, and ship games across Unreal Engine 5, Unity 6 (DOTS), Godot 4.3+, Roblox (Luau), and Web/Custom engines with senior studio-grade architectural discipline. Encompasses all 42 specialized game studio job roles across 6 departments: Game Design…
professional-game-developer
Universal production game engineering skill — design, build, profile, test, and ship games across Unreal Engine 5, Unity 6 (DOTS), Godot 4.3+, Roblox (Luau), and Web/Custom engines with senior studio-grade architectural discipline. Encompasses all 42 specialized game studio job roles across 6 departments: Game Design…
verification
Verify a Godot AI change before committing — ruff, pytest, GDScript testrun against a live editor, and live-smoke of changed tools. Use before every commit, and whenever asked to check that a change actually works.
art-generate
Generates placeholder .aseprite files from asset specs using the Aseprite MCP. Reads asset specs and art bible, creates sprites with correct dimensions/palette/layers, exports PNGs. Run after /asset-spec has produced specs and /art-bible exists.
help
Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now or I'm stuck or I don't know what to do.
qa-plan
Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when…