smoke-check

smoke-check is a skill for Codex from frabcd/codex-ai-game-studio. It costs 61 tokens per session (4,009 once invoked), scanned A, original, MIT.

A pre-QA check that runs automated tests and verifies the game's critical paths, meaning the main actions players must be able to complete. It produces a pass-or-fail report before manual quality assurance begins.

In plain words
What is it for?
Checking a sprint build, reviewing test coverage gaps, and adding platform-specific checks for PC, console, or mobile.
Why use it?
It prevents a broken build from being handed to testers and exposes missing coverage on essential functionality.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions subagents; mentions Codex; $skill-name invocation.

Good fit Checking a sprint build, reviewing test coverage gaps, and adding platform-specific checks for PC, console, or mobile.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/frabcd/codex-ai-game-studio/smoke-check
Install

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.

Any agent
npx skills add frabcd/codex-ai-game-studio --skill smoke-check
Clone the repo
git clone --depth 1 https://github.com/frabcd/codex-ai-game-studio

Made for: Codex.

Wrote 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.

agentmods badge for smoke-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/smoke-check/github.svg)](https://agentmods.dev/skills/frabcd/codex-ai-game-studio/smoke-check)
Your own site
<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/smoke-check"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/smoke-check/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.

agentmods 80×15 button for smoke-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/smoke-check"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/smoke-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,009 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Memory Poisoning · line 246
    Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.
    Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
  • medium Excessive Agency · line 419
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.04009
Opus 5 $0.00030 $0.02005
Sonnet 5 $0.00012 $0.00802
Haiku 4.5 $0.00006 $0.00401

Measured 5d ago against content hash d8e5a5fc1904, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

smoke-check 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 5d 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.

plugins/ai-game-studio/skills/smoke-check/SKILL.md · 425 lines

How it starts

The opening of the file, as written. The whole thing — 425 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 984023ddac0d5e27624f2baacde6105e45de375f under MIT; see the repository parity ledger for the exact path and blob.

Smoke Check

This skill is the gate between "implementation done" and "ready for QA hand-off". It runs the automated test suite, checks for test coverage gaps, batch-verifies critical paths with the developer, and produces a PASS/FAIL report.

The rule is simple: a build that fails smoke check does not go to QA. Handing a broken build to QA wastes their time and demoralises the team.

Output: production/qa/smoke-[date].md


Parse Arguments

Arguments can be combined: $ai-game-studio:smoke-check sprint --platform console

Base mode (first argument, default: sprint):

  • sprint — full smoke check against the current sprint's stories
  • quick — skip coverage scan (Phase 3) and Batch 3; use for rapid re-checks

Platform flag (--platform, default: none):

  • --platform pc — add PC-specific checks (keyboard, mouse, windowed mode)
  • --platform console — add console-specific checks (gamepad, TV safe zones, platform certification requirements)
  • --platform mobile — add mobile-specific checks (touch, portrait/landscape, battery/thermal behaviour)
  • --platform all — add all platform variants; output per-platform verdict table

If --platform is provided, Phase 4 adds platform-specific batches and Phase 5 outputs a per-platform verdict table in addition to the overall verdict.


Phase 1: Detect Test Setup

Before running anything, understand the environment:

  1. Test framework check: verify tests/ directory exists. If it does not: "No test directory found at tests/. Run $ai-game-studio:test-setup to scaffold the testing infrastructure, or create the directory manually if tests live elsewhere." Then stop.

  2. CI check: check whether .github/workflows/ contains a workflow file referencing tests. Note in the report whether CI is configured.

Read the full file on GitHub · 425 lines

Files

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.

Changes

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.

  1. 5d ago First seen · 425 lines · 61 tokens per session scan A d8e5a5fc1904

Subscribe to this mod's changes

smoke-check is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 4,009 once invoked, about $0.0003 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.

Related

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…

zenstory-ai/novel-to-game · 146 tokens

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.

ifBars/blender-agent-studio · 71 tokens

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.

hoatv2211/GameStudio-CodexKIT · 51 tokens

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.

hoatv2211/GameStudio-CodexKIT · 37 tokens

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.

hoatv2211/GameStudio-CodexKIT · 55 tokens

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.

SummerEngine/summer-engine-agent · 47 tokens