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/adoptnpx skills add striderZA/OpenCodeGameStudios --skill adoptgit 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/adopt)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/adopt"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/adopt.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.00078 | $0.04269 |
| Opus 5 | $0.00039 | $0.02135 |
| Sonnet 5 | $0.00016 | $0.00854 |
| Haiku 4.5 | $0.00008 | $0.00427 |
Grade A, and why
adopt 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
94% identical to adopt — 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 — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adopt — Brownfield Template Adoption
This skill audits an existing project's artifacts for format compliance with the template's skill pipeline, then produces a prioritised migration plan.
This is not /project-stage-detect.
/project-stage-detect answers: what exists?
/adopt answers: will what exists actually work with the template's skills?
A project can have GDDs, ADRs, and stories — and every format-sensitive skill will still fail silently or produce wrong results if those artifacts are in the wrong internal format.
Output: docs/adoption-plan-[date].md — a persistent, checkable migration plan.
Argument modes:
Audit mode: $ARGUMENTS[0] (blank = full)
- No argument /
full: Complete audit — all artifact types gdds: GDD format compliance onlyadrs: ADR format compliance onlystories: Story format compliance onlyinfra: Infrastructure artifact gaps only (registry, manifest, sprint-status, stage.txt)
Phase 1: Detect Project State
Emit one line before reading: "Scanning project artifacts..." — this confirms the
skill is running during the silent read phase.
Then read silently before presenting anything else.
Existence check
production/stage.txt— if present, read it (authoritative phase)design/gdd/game-concept.md— concept exists?design/gdd/systems-index.md— systems index exists?- Count GDD files:
design/gdd/*.md(excluding game-concept.md and systems-index.md) - Count ADR files:
docs/architecture/adr-*.md - Count story files:
production/epics/**/*.md(excluding EPIC.md) docs/framework/technical-preferences.md— engine configured?docs/engine-reference/— engine reference docs present?- Glob
docs/adoption-plan-*.md— note the filename of the most recent prior plan if any exist
Infer phase (if no stage.txt)
Use the same heuristic as /project-stage-detect:
- 10+ source files in
src/→ Production - Stories in
production/epics/→ Pre-Production - ADRs exist → Technical Setup
- systems-index.md exists → Systems Design
- game-concept.md exists → Concept
- Nothing → Fresh (not a brownfield project — suggest
/start)
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 · 441 lines · 78 tokens per session scan A 9a802d6b5fba
adopt is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (84 stars, last pushed 24d ago), licensed MIT. It adds 78 tokens to every session and 4,269 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to adopt, 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.
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.