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 TraftG/opencode-game-studio --skill setup-enginegit 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/setup-engine)<a href="https://agentmods.dev/skills/traftg/opencode-game-studio/setup-engine"><img src="https://agentmods.dev/badge/skills/traftg/opencode-game-studio/setup-engine/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/traftg/opencode-game-studio/setup-engine"><img src="https://agentmods.dev/badge/skills/traftg/opencode-game-studio/setup-engine.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.00045 | $0.03050 |
| Opus 5.5 | $0.00018 | $0.01220 |
| Sonnet 5.5 | $0.00009 | $0.00610 |
| Haiku 4.5 | $0.00005 | $0.00305 |
Grade A, and why
setup-engine 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 1mo 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:
- setup-engine — 91% identical, 56 lines differ
- setup-engine — 91% identical, 56 lines differ
How it starts
The opening of the file, as written. The whole thing — 328 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
Three modes:
- Full spec:
/setup-engine godot 4.6— engine and version provided - Engine only:
/setup-engine unity— engine provided, version will be looked up - No args:
/setup-engine— fully guided mode (engine recommendation + version)
2. Guided Mode (No Arguments)
If no engine is specified, run an interactive engine selection process:
Check for existing game concept
- Read
design/gdd/game-concept.mdif it exists — extract genre, scope, platform targets, art style, team size, and any engine recommendation from/brainstorm - If no concept exists, inform the user:
"No game concept found. Consider running
/brainstormfirst to discover what you want to build — it will also recommend an engine. Or tell me about your game and I can help you pick."
If the user wants to pick without a concept, ask:
- What kind of game? (2D, 3D, or both?)
- What platforms? (PC, mobile, console, web?)
- Team size and experience? (solo beginner, solo experienced, small team?)
- Any strong language preferences? (GDScript, C#, C++, GML, visual scripting?)
- Budget for engine licensing? (free only, or commercial licenses OK?)
Produce a recommendation
Use this decision matrix:
| Factor | Godot 4 | Unity | Unreal Engine 5 | GameMaker Studio 2 |
|---|---|---|---|---|
| Best for | 2D games, small 3D, solo/small teams | Mobile, mid-scope 3D, cross-platform | AAA 3D, photorealism, large teams | 2D games, pixel art, indie/small teams, rapid iteration |
| Language | GDScript (+ C#, C++ via extensions) | C# | C++ / Blueprint | GML (JavaScript-like) |
| Cost | Free, MIT license | Free under revenue threshold | Free under revenue threshold, 5% royalty | $99/year (Professional), $499/year (Studio) |
| Learning curve | Gentle | Moderate | Steep | Very gentle |
| 2D support | Excellent (native) | Good (but 3D-first engine) | Possible but not ideal | Best-in-class (purpose-built) |
| 3D support | Limited | Very good | Best-in-class | Limited (not recommended) |
| Web export | Yes (native) | Yes (limited) | No | Yes (HTML5) |
| Console export | Via third-party | Yes (with license) | Yes | Yes (Switch, PlayStation, Xbox) |
| Marketplace | Growing ecosystem | Massive | Massive | Moderate but focused on 2D |
| Prototyping speed | Fast | Moderate | Slow | Very fast |
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.
- 1mo ago First seen · 328 lines · 45 tokens per session scan A 20c7fd524c50
setup-engine is a skill published in the GitHub repository TraftG/opencode-game-studio (45 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 3,050 once invoked, about $0.0002 per session on Opus 5.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
gate-check
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
smoke-check
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
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…
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.
explore
Pre-workflow rapid prototyping for exploring multiple game ideas before committing to a development workflow. Produces lightweight reports with no workflow commitment.