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/striderza/opencodegamestudios/explorenpx skills add striderZA/OpenCodeGameStudios --skill exploregit clone --depth 1 https://github.com/striderZA/OpenCodeGameStudiosWrote 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/striderza/opencodegamestudios/explore)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/explore"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/explore.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.00030 | $0.02094 |
| Opus 5 | $0.00015 | $0.01047 |
| Sonnet 5 | $0.00006 | $0.00419 |
| Haiku 4.5 | $0.00003 | $0.00209 |
Grade A, and why
explore 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 yesterday.
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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill is the pre-workflow exploration lane. Use it when you have one or more rough game ideas and want to validate them before choosing between the Hybrid workflow (lean, iterative) or the Full OCGS workflow (formal, structured).
When to use /explore:
- You have 2-4 rough ideas and want to feel them out before committing
- You are not sure if your concept is fun, feasible, or scoped correctly
- You want to avoid formal process overhead until you know what you're making
When NOT to use /explore:
- You already know your game and are ready to build → use
/startdirectly - You are in the middle of production → use
/prototypeor/hybrid-prototype - You need a formal vertical slice → use
/prototypewithin the full workflow
Key properties:
- No workflow commitment: Does not create
production/stage.txt,production/review-mode.txt, or any production artifacts - No process overhead: No GDDs, no ADRs, no architecture, no sprint plans
- Time-boxed: 1-2 days per idea maximum
- Isolated: All work lives in
prototypes/explore/[idea-name]/ - Composable: Run it multiple times for multiple ideas, then compare results
Agents involved: prototyper only. No director reviews, no multi-tier coordination.
Phase 1: Define the Question (5 minutes)
Read the concept description from the argument. State the one core question this prototype must answer. If the concept is vague, ask the user to clarify before proceeding.
Examples of good questions:
- "Does the core loop of harvesting + crafting feel satisfying for 10 minutes?"
- "Is the combat pace too slow or too frantic with 3 enemy types?"
- "Does the movement mechanic make exploration feel good, or tedious?"
Bad question: "Is this game fun?" (Too broad. Narrow it down to one mechanic or feeling.)
Ask the user: "The core question for this prototype is: [question]. Proceed?"
Phase 2: Plan (15 minutes)
Define the minimum viable prototype in 3-5 bullet points:
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.
- yesterday First seen · 218 lines · 30 tokens per session scan A 1ac35af836c6
explore is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (83 stars, last pushed 24d ago), licensed MIT. It adds 30 tokens to every session and 2,094 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
generated-raster-asset-pipeline
Define acceptance, validation, and runtime integration rules for raster assets generated with image models before they become real project content.
lighting-lod-pipeline
Define lighting policy, light budgets, LOD chains, and culling rules so 3D scenes look intentional and hit frame budgets.
2d-animation-pipeline
Define authoring, import, and state machine rules for frame-by-frame and skeletal 2D animations.
sprite-pipeline
Define import, slicing, atlas packing, and naming rules for 2D sprite assets.
ui-animation-pipeline
Define transition, feedback, and state-driven animation rules for UI elements.
tilemap-pipeline
Define tileset creation, auto-tile rules, collision shapes, and tilemap configuration for 2D levels.