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 IdoCohen560/claude-unity-game-studio --skill smoke-checkgit clone --depth 1 https://github.com/IdoCohen560/claude-unity-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/idocohen560/claude-unity-game-studio/smoke-check)<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/smoke-check"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-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.
<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/smoke-check"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/smoke-check.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.00061 | $0.03798 |
| Opus 5 | $0.00030 | $0.01899 |
| Sonnet 5 | $0.00012 | $0.00760 |
| Haiku 4.5 | $0.00006 | $0.00380 |
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 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.
This is a copy
94% identical to smoke-check — 10 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 — 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 storiesquick— 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 attests/. Run/test-setupto 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
.claude/docs/technical-preferences.mdand extract theEngine:value. Store this for test command selection in Phase 2. -
Smoke test list: check whether
production/qa/smoke-tests.mdortests/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).
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 · 418 lines · 61 tokens per session scan A c741330676ba
smoke-check is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (19 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 3,798 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to smoke-check, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
mvp-readiness
Runs a structured MVP quality-gate audit covering stability, security, logging, docs, and implementation integrity. Reports pass/fail with evidence.
requirements-generator
Generates structured requirements documents with functional and non-functional requirements, Gherkin acceptance criteria, edge cases, and out-of-scope items.
test-writer
Generates comprehensive unit and integration tests for a given file or function, auto-detecting the project test framework and matching existing test style.
abd-test
ABD Testing agent: auto-detects the test framework, writes tests matching project style, runs the suite, and records a test artifact.
plan-qa
Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA- - .md) that /execute-qa…
execute-qa
Executes a QA specification (specs/qa/QA- - .md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact…