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 striderZA/OpenCodeGameStudios --skill map-systemsgit 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/map-systems)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/map-systems"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/map-systems/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/striderza/opencodegamestudios/map-systems"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/map-systems.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.00026 | $0.03684 |
| Opus 5.5 | $0.00010 | $0.01474 |
| Sonnet 5.5 | $0.00005 | $0.00737 |
| Haiku 4.5 | $0.00003 | $0.00368 |
Grade A, and why
map-systems 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.
This is a copy
95% identical to map-systems — 184 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When this skill is invoked:
Parse Arguments
Two modes:
- No argument:
/map-systems— Run the full decomposition workflow (Phases 1-5) to create or update the systems index. next:/map-systems next— Pick the highest-priority undesigned system from the index and hand off to/design-system(Phase 6).
Also 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.
Phase 1: Read Concept (Required Context)
Read the game concept and any existing design work. This provides the raw material for systems decomposition.
Required:
- Read
design/gdd/game-concept.md— fail with a clear message if missing:"No game concept found at
design/gdd/game-concept.md. Run/concept-brainstormfirst to create one, then come back to decompose it into systems."
Optional (read if they exist):
- Read
design/gdd/game-pillars.md— pillars constrain priority and scope - Read
design/gdd/systems-index.md— if exists, resume from where it left off (update, don't recreate from scratch) - Glob
design/gdd/*.md— check which system GDDs already exist
If the systems index already exists:
- Read it and present current status to the user
- Use
questionto ask: "The systems index already exists with [N] systems ([M] designed, [K] not started). What would you like to do?"- Options: "Update the index with new systems", "Design the next undesigned system", "Review and revise priorities"
Phase 2: Systems Enumeration (Collaborative)
Extract and identify all systems the game needs. This is the creative core of the skill — it requires human judgment because concept docs rarely enumerate every system explicitly.
Step 2a: Extract Explicit Systems
Scan the game concept for directly mentioned systems and mechanics:
- Core Mechanics section (most explicit)
- Core Loop section (implies what systems drive each loop tier)
- Technical Considerations section (networking, procedural generation, etc.)
- MVP Definition section (required features = required 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.
- 1mo ago First seen · 364 lines · 26 tokens per session scan A f3a2902c0ae6
map-systems is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (99 stars, last pushed 13d ago), licensed MIT. It adds 26 tokens to every session and 3,684 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to map-systems, differing in 184 lines, and is treated as a copy.
Other skills, from other repositories
professional-game-developer
Universal production game engineering skill — design, build, profile, test, and ship games across Unreal Engine 5, Unity 6 (DOTS), Godot 4.3+, Roblox (Luau), and Web/Custom engines with senior studio-grade architectural discipline. Encompasses all 42 specialized game studio job roles across 6 departments: Game Design…
design-system
Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.
setup-engine
Configure the project's game engine and version. Pins the engine in OPENCODE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
gate-check
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts.
reverse-document
Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.
estimate
Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.