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 frabcd/codex-ai-game-studio --skill regression-suitegit clone --depth 1 https://github.com/frabcd/codex-ai-game-studioWrote 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/frabcd/codex-ai-game-studio/regression-suite)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/regression-suite"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/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.1 | $0.00047 | $0.02304 |
| Opus 5 | $0.00023 | $0.01152 |
| Sonnet 5 | $0.00009 | $0.00461 |
| Haiku 4.5 | $0.00005 | $0.00230 |
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 7d 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
89% identical to regression-suite — 36 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Port provenance: adapted from the pinned upstream source at
984023ddac0d5e27624f2baacde6105e45de375funder MIT; see the repository parity ledger for the exact path and blob.
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 (
$ai-game-studio:gate-check polishrequires regression suite exists) - As part of sprint close to detect coverage drift
1. Parse Arguments
Modes:
$ai-game-studio:regression-suite update— scan new bug fixes this sprint and check for regression test presence; add new tests to the suite manifest$ai-game-studio:regression-suite audit— full audit of all GDD critical paths vs. existing test coverage; flag paths with no regression test$ai-game-studio:regression-suite report— read-only status report (no writes); suitable for sprint reviews- No argument — if a sprint is clearly active (sprint plan exists with in-progress stories), run
update. If ambiguous or no active sprint is detected, usethe available user-input mechanism:- Prompt: "No subcommand specified. Which mode do you want to run?"
- Options:
[A] update — scan new bug fixes this sprint and add missing regression tests[B] audit — full audit of all GDD critical paths vs. existing test coverage[C] report — read-only status report (no writes)
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
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 259 lines · 47 tokens per session scan A d06b6d681069
regression-suite is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 2,304 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to regression-suite, differing in 36 lines, and is treated as a copy.
Other skills, from other repositories
game-qa
Verify a game with evidence on its selected target runtime. Launch the actual build and prove real rendering, input, the core loop, at least one designed outcome, restart, and explicit limitations without dressing subjective fun up as a certain verdict. Use for test a generated game, QA a game build, check whether the…
blender-asset-validation
Inspect and validate Blender assets technically and visually. Use for .blend, .glb, .gltf, .fbx, or .obj quality checks; topology and export review; evaluated triangle/material/hierarchy metrics; standardized multiview renders; fresh-import verification; or evidence-backed review of an agent-generated mesh.
platform-device-compatibility-matrix
Use when a game needs a platform and device compatibility matrix across OS, hardware, GPU, memory, resolution, input, network, storefront, certification, test evidence, and support policy; not for store metadata preparation.
playtest-evidence
Use when planning or reviewing game playtests that need structured scenarios, participant context, observations, reproduction evidence, severity, and honest separation of observed findings from conclusions.
qa-test-strategy-and-coverage
Use when a game project, milestone, or feature needs a QA test strategy and coverage matrix across risk, test levels, platforms, environments, ownership, automation, regression, evidence, and exit criteria; not for one playtest session.
playtesting-a-feature
Use when about to claim a gameplay feature is done, shipped, or working — requires actually running the game and walking through the feature before declaring completion. Static diagnostics and type checks do not count as playtesting.