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/create-epicsnpx skills add striderZA/OpenCodeGameStudios --skill create-epicsgit 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/create-epics)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/create-epics"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/create-epics.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.00061 | $0.02148 |
| Opus 5 | $0.00030 | $0.01074 |
| Sonnet 5 | $0.00012 | $0.00430 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade A, and why
create-epics 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.
This is a copy
86% identical to create-epics — 32 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Epics
An epic is a named, bounded body of work that maps to one architectural module. It defines what needs to be built and who owns it architecturally. It does not prescribe implementation steps — that is the job of stories.
Run this skill once per layer as you approach that layer in development. Do not create Feature layer epics until Core is nearly complete — the design will have changed.
Output: production/epics/[epic-slug]/EPIC.md + production/epics/index.md
Next step after each epic: /create-stories [epic-slug]
When to run: After /create-control-manifest and /architecture-review pass.
1. Parse Arguments
Resolve the review mode (once, store for all gate spawns this run):
- If
--review [full|lean|solo]was passed → use that - Else read
production/review-mode.txt→ use that value - Else → default to
lean
See docs/framework/director-gates.md for the full check pattern.
Modes:
/create-epics all— process all systems in layer order/create-epics layer: foundation— Foundation layer only/create-epics layer: core— Core layer only/create-epics layer: feature— Feature layer only/create-epics layer: presentation— Presentation layer only/create-epics [system-name]— one specific system- No argument — ask: "Which layer or system would you like to create epics for?"
2. Load Inputs
Step 2a — Summary scan (fast)
Grep all GDDs for their ## Summary sections before reading anything fully:
Grep pattern="## Summary" glob="design/gdd/*.md" output_mode="content" -A 5
For layer: or [system-name] modes: filter to only in-scope GDDs based on
the Summary quick-reference. Skip full-reading anything out of scope.
Step 2b — Full document load (in-scope systems only)
Using the Step 2a grep results, identify which systems are in scope. Read full documents only for in-scope systems — do not read GDDs or ADRs for out-of-scope systems or layers.
Read for in-scope systems:
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 · 226 lines · 61 tokens per session scan A b95c0b980c35
create-epics is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (84 stars, last pushed 24d ago), licensed MIT. It adds 61 tokens to every session and 2,148 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to create-epics, differing in 32 lines, and is treated as a copy.
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.
tilemap-pipeline
Define tileset creation, auto-tile rules, collision shapes, and tilemap configuration for 2D levels.
game-feel-design
Design moment-to-moment feedback — hit-stop, screen shake, tweening, and response timing — so actions feel readable and satisfying.
combat-design
Design combat verbs, enemy pressure, resource economy, readability, and tuning hooks.
level-design
Shape level flow, pacing, navigation, encounter staging, and spatial teaching.
monetization-design
Design monetization systems that fit the product, respect player trust, and remain technically and legally manageable.