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/review-all-gddsnpx skills add striderZA/OpenCodeGameStudios --skill review-all-gddsgit 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/review-all-gdds)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/review-all-gdds"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/review-all-gdds.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.00073 | $0.06128 |
| Opus 5 | $0.00036 | $0.03064 |
| Sonnet 5 | $0.00015 | $0.01226 |
| Haiku 4.5 | $0.00007 | $0.00613 |
Grade A, and why
review-all-gdds 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
88% identical to review-all-gdds — 25 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 — 629 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review All GDDs
This skill reads every system GDD simultaneously and performs two complementary reviews that cannot be done per-GDD in isolation:
- Cross-GDD Consistency — contradictions, stale references, and ownership conflicts between documents
- Game Design Holism — issues that only emerge when you see all systems together: dominant strategies, broken economies, cognitive overload, pillar drift, competing progression loops
This is distinct from /design-review, which reviews one GDD for internal
completeness. This skill reviews the relationships between all GDDs.
When to run:
- After all MVP-tier GDDs are individually approved
- After any GDD is significantly revised mid-production
- Before
/create-architecturebegins (architecture built on inconsistent GDDs inherits those inconsistencies)
Argument modes:
Focus: $ARGUMENTS[0] (blank = full)
- No argument /
full: Both consistency and design theory passes consistency: Cross-GDD consistency checks only (faster)design-theory: Game design holism checks onlysince-last-review: Only GDDs modified since the last review report (git-based)
Phase 1: Load Everything
Phase 1a — L0: Summary Scan (fast, low tokens)
Before reading any full document, use Grep to extract ## Summary sections
from all GDD files:
Grep pattern="## Summary" glob="design/gdd/*.md" output_mode="content" -A 5
Display a manifest to the user:
Found [N] GDDs. Summaries:
• combat.md — [summary text]
• inventory.md — [summary text]
...
For since-last-review mode: run git log --name-only to identify GDDs
modified since the last review report file was written. Show the user which
GDDs are in scope based on summaries before doing any full reads. Only
proceed to L1 for those GDDs plus any GDDs listed in their "Key deps".
Phase 1b — Registry Pre-Load (fast baseline)
Before full-reading any GDD, check for the entity registry:
Read path="design/registry/entities.yaml"
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 · 629 lines · 73 tokens per session scan A 4f481b478c05
review-all-gdds is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (84 stars, last pushed 24d ago), licensed MIT. It adds 73 tokens to every session and 6,128 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to review-all-gdds, differing in 25 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.
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.