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/regression-suitenpx skills add striderZA/OpenCodeGameStudios --skill regression-suitegit 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/regression-suite)<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/regression-suite"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/regression-suite.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.00047 | $0.02076 |
| Opus 5 | $0.00023 | $0.01038 |
| Sonnet 5 | $0.00009 | $0.00415 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade A, and why
regression-suite 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 regression-suite — 10 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regression Suite
This skill ensures that every bug fix is backed by a test that would have caught the original bug — and that the regression suite stays current as the game evolves. It also detects when new features have been added without corresponding regression coverage.
A regression suite is not a new test category — it is a curated list of
tests already in tests/ that collectively cover the game's critical paths
and known failure points. This skill maintains that list.
Output: tests/regression-suite.md
When to run:
- After fixing a bug (confirm a regression test was written or identify gap)
- Before a release gate (
/gate-check polishrequires regression suite exists) - As part of sprint close to detect coverage drift
1. Parse Arguments
Modes:
/regression-suite update— scan new bug fixes this sprint and check for regression test presence; add new tests to the suite manifest/regression-suite audit— full audit of all GDD critical paths vs. existing test coverage; flag paths with no regression test/regression-suite report— read-only status report (no writes); suitable for sprint reviews- No argument — run
updateif a sprint is active, elseaudit
2. Load Context
Step 2a — Load existing regression suite
Read tests/regression-suite.md if it exists. Extract:
- Total registered regression tests
- Last updated date
- Any tests flagged as
STALEorQUARANTINED
If it does not exist: note "No regression suite found — will create one."
Step 2b — Load test inventory
Glob all test files:
tests/unit/**/*_test.*
tests/integration/**/*_test.*
tests/regression/**/*
For each file, note the system (from directory path) and file name. Do not read test file contents unless needed for name-to-test mapping.
Step 2c — Load GDD critical paths
For audit mode: read design/gdd/systems-index.md to get all systems.
For each MVP-tier system, read its GDD and extract:
- Acceptance Criteria (these define the critical paths)
- Formulas section (formulas must have regression tests)
- Edge Cases section (known edge cases should have regression tests)
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 · 251 lines · 47 tokens per session scan A e5f923ba3224
regression-suite is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (84 stars, last pushed 24d ago), licensed MIT. It adds 47 tokens to every session and 2,076 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 regression-suite, differing in 10 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.
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.
ui-animation-pipeline
Define transition, feedback, and state-driven animation rules for UI elements.
tilemap-pipeline
Define tileset creation, auto-tile rules, collision shapes, and tilemap configuration for 2D levels.