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 merlinhu1/codex-game-studio --skill cgs-test-helpersgit clone --depth 1 https://github.com/merlinhu1/codex-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/merlinhu1/codex-game-studio/cgs-test-helpers)<a href="https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-test-helpers"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-test-helpers/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-test-helpers"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-test-helpers.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.00582 |
| Opus 5 | $0.00023 | $0.00291 |
| Sonnet 5 | $0.00009 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
cgs-test-helpers 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 6d 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.
What it actually says
Codex Game Studio Test Helpers
Use this skill for test helpers work in Template Game.
Objective
Design reusable test helpers without hiding assertions, over-mocking, or coupling tests to implementation details.
Inputs
- AGENTS.md
- .codex/studio.json
- task-relevant files named by the user or task record
- design/gdd.md
- production/session-state/active.md
- tests/
Arguments
- Objective or user request.
- Target files, scenes, assets, or docs.
- Constraints, deadlines, acceptance criteria, and verification command when known.
Procedure
- Clarify the requested design reusable test helpers without hiding assertions, over-mocking, or coupling tests to implementation details. and identify the current project stage.
- Collect evidence for Helper Purpose, Assertion Boundary, Fixture Shape.
- Run or define the focused validation loop before reporting conclusions.
- Produce the requested artifact or review with clear file paths and verification evidence.
Write Targets
- tests/
- production/session-state/
- prototypes/
Output Contract
- Summary
- Helper Purpose
- Assertion Boundary
- Fixture Shape
- Misuse Guard
- Risks
- Changed files or proposed files
- Verification evidence
- Next owner or decision
Quality Gates
- Helper Purpose
- Assertion Boundary
- Fixture Shape
- Misuse Guard
- Scope remains bounded to the current task and project stage.
- Report labels unverified assumptions separately from evidence.
Decision Gates
- Continue only when the expected output can be verified or clearly labeled as a plan.
- Escalate to producer or qa-playtester when scope, ownership, or acceptance evidence is ambiguous.
- Stop before broad rewrites, generated prompt mirrors, or hidden lifecycle behavior.
Handoff
Report changed files, verification evidence, remaining risks, and the next owner or decision. Do not imply hidden hooks or autonomous background work.
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.
- 6d ago First seen · 81 lines · 45 tokens per session scan A ef144b06a495
cgs-test-helpers is a skill published in the GitHub repository merlinhu1/codex-game-studio (54 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 582 once invoked, about $0.0002 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 skills, from other repositories
javascript-testing-patterns
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
test-helpers
Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.
tests-run
Execute Unity tests (EditMode or PlayMode) and return per-test results. Supports filtering by test assembly, namespace, class, and method. Refreshes the AssetDatabase first; defers execution across domain reloads if scripts changed. Precondition: every open scene must be saved — dirty scenes abort the run.
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
testing
Use this skill when writing, reviewing, or improving tests in WrongStack. Triggers: user says "test", "unit test", "integration test", "e2e", "mock", "vitest", "coverage", "assert", "expect", "test strategy", "write tests".
test-generator
Generate test templates for unit tests, integration tests, and UI tests using Swift Testing and XCTest. Use when adding tests to iOS/macOS apps.