A quick release gate that runs automated tests and checks the game's critical paths before it is handed to manual QA. A failing result means the build is not ready for broader testing.

It helps verify sprint work, check core functionality, identify test-coverage gaps, and add checks for PC, console, or mobile requirements.

Sending a broken build to QA wastes testing time and can hide basic failures among more detailed reports. This catches major problems first and records a pass-or-fail result.

smoke-check — Skill for Claude Code and Codex by striderZA: A quick release gate that runs automated tests and…

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.

agentmods

npx agentmods add skills/striderza/opencodegamestudios/smoke-check

Any agent

npx skills add striderZA/OpenCodeGameStudios --skill smoke-check

Clone the repo

git clone --depth 1 https://github.com/striderZA/OpenCodeGameStudios

Made for: Claude Code, 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/striderza/opencodegamestudios/smoke-check.svg)](https://agentmods.dev/skills/striderza/opencodegamestudios/smoke-check)

Your own site

<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/smoke-check"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/smoke-check.svg" alt="Measured on agentmods" 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 3,790 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00061	$0.03790
Opus 5	$0.00030	$0.01895
Sonnet 5	$0.00012	$0.00758
Haiku 4.5	$0.00006	$0.00379

Measured yesterday against content hash 29dcaa5034b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

smoke-check — 94% identical, 10 lines differ

.agents/modules/qa/skills/smoke-check/SKILL.md · 418 lines

How it starts

The opening of the file, as written. The whole thing — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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: /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:

Test framework check: verify tests/ directory exists. If it does not: "No test directory found at tests/. Run /test-setup to scaffold the testing infrastructure, or create the directory manually if tests live elsewhere." Then stop.
CI check: check whether .github/workflows/ contains a workflow file referencing tests. Note in the report whether CI is configured.
Engine detection: read docs/framework/technical-preferences.md and extract the Engine: value. Store this for test command selection in Phase 2.
Smoke test list: check whether production/qa/smoke-tests.md or tests/smoke/ exists. If a smoke test list is found, load it for use in Phase 4. If neither exists, smoke tests will be drawn from the current QA plan (Phase 4 fallback).

Read the full file on GitHub · 418 lines

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.

yesterday First seen · 418 lines · 61 tokens per session scan A 29dcaa5034b2

Subscribe to this mod's changes

smoke-check is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (84 stars, last pushed 24d ago), licensed MIT. It adds 61 tokens to every session and 3,790 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.

E2E testing Game development Testing ai-agents aseprite claude-code game-development godot

yume-visual-tester

Auto-generates a visualtestplan.json for a given game + level. Reads the GDD's aesthetic targets, the level's entities.json, the session's git diff, the assertion library, and the priors library — emits a concrete list of 10-15 visual tests that the ADR 0056 runner can execute. Distinct from yume-visual-designer…

kamwoh/yume · 119 tokens

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.

dcc-mcp/dcc-mcp-godot · 55 tokens

hearth-playtest

Let the engine hunt bugs for you — bot playtesting via hearth sweep. Seeded bot policies (mash/idle/wander/seek) play a scene headlessly across many seeds and report softlocks, crashes, stuck states, and unmet objectives as a compact evidence report; objectives double as executable acceptance criteria; a failing seed…

echoo19/hearth · 112 tokens

smoke-check