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/frabcd/codex-ai-game-studio/test-setupnpx skills add frabcd/codex-ai-game-studio --skill test-setupgit 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/test-setup)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/test-setup"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/test-setup.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.00049 | $0.03124 |
| Opus 5 | $0.00024 | $0.01562 |
| Sonnet 5 | $0.00010 | $0.00625 |
| Haiku 4.5 | $0.00005 | $0.00312 |
Grade A, and why
test-setup 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 2d 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
95% identical to test-setup — 40 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 — 429 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.
Test Setup
This skill scaffolds the automated testing infrastructure for the project. It detects the configured engine, generates the appropriate test runner configuration, creates the standard directory layout, and wires up CI/CD so tests run on every push.
Run this once during the Technical Setup phase, before any implementation begins. A test framework installed at sprint start costs 30 minutes. A test framework installed at sprint four costs 3 sprints.
Output: tests/ directory structure + .github/workflows/tests.yml
Phase 1: Detect Engine and Existing State
-
Read engine config:
- Read
.ai-game-studio/project.jsonand extract theEngine:value. - If engine is not configured (
[TO BE CONFIGURED]), stop: "Engine not configured. Run$ai-game-studio:setup-enginefirst, then re-run$ai-game-studio:test-setup."
- Read
-
Check for existing test infrastructure:
- file discovery
tests/— does the directory exist? - file discovery
tests/unit/andtests/integration/— do subdirectories exist? - file discovery
.github/workflows/— does a CI workflow file exist? - file discovery
tests/gdunit4_runner.gd(Godot) ortests/EditMode/(Unity) orSource/Tests/(Unreal) for engine-specific artifacts.
- file discovery
-
Report findings:
- "Engine: [engine]. Test directory: [found / not found]. CI workflow: [found / not found]."
- If everything already exists AND
forceargument was not passed: "Test infrastructure appears to be in place. Re-run with$ai-game-studio:test-setup forceto regenerate. Proceeding will not overwrite existing test files."
If the force argument is passed, skip the "already exists" early-exit and
proceed — but still do not overwrite files that already exist at a given path.
Only create files that are missing.
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.
- 2d ago First seen · 429 lines · 49 tokens per session scan A 8837705d8034
test-setup is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 3,124 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to test-setup, differing in 40 lines, and is treated as a copy.
Other skills, from other repositories
ci-workflow
Design and maintain .NET CI workflows for F#, C#, and mixed solutions with SDK setup, restore, build, test, format checks, package checks, caching, and matrix decisions.
ci-setup
Set up CI/CD integration for automated DeployGate uploads and PR-based distribution.
dockerized-service-release-deployment-workflow
Create a Dockerized-service release contract with clean GitHub Actions builds, main-anchored tags, immutable digest manifests, published-release deployments, production approval, health checks, and exact-digest rollback.
scaffolding
Use for scaffolding, new projects, package setup, quality tooling, CI, repo structure.
diagnosing-ci-and-merge-bottlenecks
Diagnoses CI and pull-request pipeline health for a GitHub repo using the engineering analytics MCP tools — pull-requests (PR list with CI status), workflow-health (per-workflow CI trends), and pr-lifecycle (a single PR's timeline). Use when asked whether CI is getting faster or slower, which GitHub Actions workflow…
cicd
This skill should be used when the user mentions keywords related to cicd.