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-architecturenpx skills add striderZA/OpenCodeGameStudios --skill create-architecturegit 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-architecture)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/create-architecture"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/create-architecture.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.00068 | $0.03469 |
| Opus 5 | $0.00034 | $0.01734 |
| Sonnet 5 | $0.00014 | $0.00694 |
| Haiku 4.5 | $0.00007 | $0.00347 |
Grade A, and why
create-architecture 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
84% identical to create-architecture — 104 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Architecture
This skill produces docs/architecture/architecture.md — the master architecture
document that translates all approved GDDs into a concrete technical blueprint.
It sits between design and implementation, and must exist before sprint planning begins.
Distinct from /architecture-decision: ADRs record individual point decisions.
This skill creates the whole-system blueprint that gives ADRs their context.
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.
Argument modes:
- No argument /
full: Full guided walkthrough — all sections, start to finish layers: Focus on the system layer diagram onlydata-flow: Focus on data flow between modules onlyapi-boundaries: Focus on API boundary definitions onlyadr-audit: Audit existing ADRs for engine compatibility gaps only
Phase 0: Load All Context
Before anything else, load the full project context in this order:
0a. Engine Context (Critical)
Read the engine reference library completely:
docs/engine-reference/[engine]/VERSION.md→ Extract: engine name, version, LLM cutoff, post-cutoff risk levelsdocs/engine-reference/[engine]/breaking-changes.md→ Extract: all HIGH and MEDIUM risk changesdocs/engine-reference/[engine]/deprecated-apis.md→ Extract: APIs to avoiddocs/engine-reference/[engine]/current-best-practices.md→ Extract: post-cutoff best practices that differ from training data- All files in
docs/engine-reference/[engine]/modules/→ Extract: current API patterns per domain
If no engine is configured, stop and prompt:
"No engine is configured. Run
/setup-enginefirst. Architecture cannot be written without knowing which engine and version you are targeting."
0b. Design Context + Technical Requirements Extraction
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 · 403 lines · 68 tokens per session scan A 6e30d131830e
create-architecture is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (84 stars, last pushed 24d ago), licensed MIT. It adds 68 tokens to every session and 3,469 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to create-architecture, differing in 104 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.
ui-animation-pipeline
Define transition, feedback, and state-driven animation rules for UI elements.
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.
tilemap-pipeline
Define tileset creation, auto-tile rules, collision shapes, and tilemap configuration for 2D levels.