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 commands/striderza/opencodegamestudios/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/commands/striderza/opencodegamestudios/propagate-design-change)<a href="https://agentmods.dev/commands/striderza/opencodegamestudios/propagate-design-change"><img src="https://agentmods.dev/badge/commands/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.00015 | $0.00042 |
| Opus 5 | $0.00008 | $0.00021 |
| Sonnet 5 | $0.00003 | $0.00008 |
| Haiku 4.5 | $0.00002 | $0.00004 |
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.
What it actually says
Invokes /propagate-design-change skill.
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 · 9 lines · 15 tokens per session scan A c001a515cdf3
propagate-design-change is a command published in the GitHub repository striderZA/OpenCodeGameStudios (83 stars, last pushed 24d ago), licensed MIT. It adds 15 tokens to every session and 42 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
game-feel-pass
Review moment-to-moment feedback, response timing, and juice so core actions feel readable and satisfying.
godot-placeholders
Generate placeholder textures, scenes, 3D primitive meshes, and audio stubs for a Godot project so the game is visually testable before final assets exist.
input-review
Review input handling, device coverage, buffering, and control responsiveness from an engine-neutral perspective.
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
bug-triage
Classify bugs, assign severity and priority, and propose next actions.
cert-check
Review the current state against certification and platform compliance expectations.