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-flakinessgit 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-flakiness)<a href="https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-test-flakiness"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-test-flakiness/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-flakiness"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-test-flakiness.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.00047 | $0.00584 |
| Opus 5.5 | $0.00019 | $0.00234 |
| Sonnet 5.5 | $0.00009 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
cgs-test-flakiness 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 1mo 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 Flakiness
Use this skill for test flakiness work in Template Game.
Objective
Diagnose flaky tests by isolating timing, randomness, ordering, environment, and cleanup causes.
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 diagnose flaky tests by isolating timing, randomness, ordering, environment, and cleanup causes. and identify the current project stage.
- Collect evidence for Failure Pattern, Isolation, Root Cause.
- 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
- Failure Pattern
- Isolation
- Root Cause
- Stabilization
- Risks
- Changed files or proposed files
- Verification evidence
- Next owner or decision
Quality Gates
- Failure Pattern
- Isolation
- Root Cause
- Stabilization
- 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.
- 1mo ago First seen · 81 lines · 47 tokens per session scan A 4cbdae719faf
cgs-test-flakiness is a skill published in the GitHub repository merlinhu1/codex-game-studio (75 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 584 once invoked, about $0.0002 per session on Opus 5.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
smoke-check
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
test-fix
Automatically invoke when any test run produces failures: FAIL output, test errors, or assertion failures in unit or E2E suites. Do NOT wait for the user to ask. Hard limit of 3 fix attempts per failure, then stops and escalates. Trigger on: "tests are failing", "fix the tests", "tests are broken".
godot-testing-qa
Domain skill — Run a sequence of runtime actions and assertions. Assert runtime node existence and properties. Assert visible runtime text. Compare two PNGs using bounded pixel sampling. Sample runtime performance for a bounded frame count. Return the latest runtime test report. Gate collision acceptance on…
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
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.