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/propagate-design-changenpx skills add striderZA/OpenCodeGameStudios --skill propagate-design-changegit 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/propagate-design-change)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/propagate-design-change"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/propagate-design-change.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.00044 | $0.01906 |
| Opus 5 | $0.00022 | $0.00953 |
| Sonnet 5 | $0.00009 | $0.00381 |
| Haiku 4.5 | $0.00004 | $0.00191 |
Grade A, and why
propagate-design-change 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
97% identical to propagate-design-change — 5 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propagate Design Change
When a GDD changes, architectural decisions written against it may no longer be valid. This skill finds every affected ADR, compares what the ADR assumed against what the GDD now says, and guides the user through resolution.
Usage: /propagate-design-change design/gdd/combat-system.md
1. Validate Argument
A GDD path argument is required. If missing, fail with:
"Usage:
/propagate-design-change design/gdd/[system].mdProvide the path to the GDD that was changed."
Verify the file exists. If not, fail with:
"[path] not found. Check the path and try again."
2. Read the Changed GDD
Read the current GDD in full.
3. Read the Previous Version
Run git to get the previous committed version:
git show HEAD:design/gdd/[filename].md
If the file has no git history (new file), report:
"No previous version in git — this appears to be a new GDD, not a revision. Nothing to propagate."
If git returns the previous version, do a conceptual diff:
- Identify sections that changed (new rules, removed rules, modified formulas, changed acceptance criteria, changed tuning knobs)
- Identify sections that are unchanged
- Produce a change summary:
## Change Summary: [GDD filename]
Date of revision: [today]
Changed sections:
- [Section name]: [what changed — new rule, removed rule, formula modified, etc.]
Unchanged sections:
- [Section name]
Key changes affecting architecture:
- [Change 1 — likely to affect ADRs]
- [Change 2]
4. Load Architecture Inputs
Read all ADRs in docs/architecture/:
- For each ADR, read the full file
- Extract the "GDD Requirements Addressed" table
- Note which GDD documents and requirement IDs each ADR references
Read docs/architecture/architecture-traceability.md if it exists.
Report: "Loaded [N] ADRs. [M] reference [gdd filename]."
5. Impact Analysis
For each ADR that references the changed GDD:
Compare the ADR's "GDD Requirements Addressed" entries against the changed sections of the GDD. For each referenced requirement:
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 · 239 lines · 44 tokens per session scan A e0145ee67521
propagate-design-change is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (83 stars, last pushed 24d ago), licensed MIT. It adds 44 tokens to every session and 1,906 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to propagate-design-change, differing in 5 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.
dialogue-content-pipeline
Manage dialogue and text content so it remains editable, implementable, localizable, and testable.
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.