A pre-QA smoke test that runs the automated checks and verifies the application's most important user flows. A smoke test is a short check that the main path still works.

Use it to check app launch, sign-in or guest access, the primary action, backgrounding, state recovery, and sign-out on a simulator, emulator, or device.

It stops a broken build from reaching lengthy manual QA and produces a clear pass or fail result.

smoke-check — Skill for Claude Code by cenconq25

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 cenconq25/claude-code-app-studio --skill smoke-check

Clone the repo

git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

Made for: Claude Code.

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/cenconq25/claude-code-app-studio/smoke-check/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/smoke-check)

Your own site

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/smoke-check"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/smoke-check"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/smoke-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,508 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.

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.1	$0.00052	$0.01508
Opus 5	$0.00026	$0.00754
Sonnet 5	$0.00010	$0.00302
Haiku 4.5	$0.00005	$0.00151

Measured 6d ago against content hash e7acef822fb9, 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 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.

.claude/skills/smoke-check/SKILL.md · 198 lines

How it starts

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

Smoke Check

A short, blocking gate that runs before manual QA invests time. If smoke fails, manual QA stops and the build goes back to engineering.

Phase 1: Confirm Build and Target

Parse --build (path to .ipa / .apk / app bundle) and --target (sim, emulator, or attached device). If neither is given, infer:

React Native: prompt to run npx react-native run-ios or run-android.
Flutter: prompt to run flutter run against the target.
iOS native: locate the most recent build under ~/Library/Developer/Xcode/DerivedData.
Android native: locate the most recent app-debug.apk under app/build/outputs/apk/.

Confirm with the user before launching anything.

Phase 2: Read the Smoke Spec

Read tests/smoke/critical-paths.md. This file is authored by /qa-plan and lists the smoke flows for the current sprint.

If missing, fall back to the default smoke set:

Cold start within the budgeted ms.
App reaches a stable home/landing screen.
Sign-in (or guest path) succeeds.
Primary CTA on home reaches its destination without a crash.
App backgrounds and foregrounds without state loss.
Sign-out completes cleanly.

Surface the spec to the user and confirm scope.

Phase 3: Run the Automated Suite

Run the unit + integration test suite first. The smoke gate is "build is shippable for manual QA", so a red automated suite is automatic FAIL.

Per framework via Bash:

React Native: npx jest --silent --reporters=default --bail=false
Flutter: flutter test --machine
iOS: xcodebuild test -scheme [scheme] -destination 'platform=iOS Simulator,name=[device]'
Android: ./gradlew testDebugUnitTest connectedAndroidTest

Capture pass/fail counts and any failure output.

If the unit or integration suite fails, stop here with verdict FAIL and list the failing tests.

Phase 4: Run E2E Smoke Flows

For each smoke flow in the spec, run the corresponding automated flow:

Maestro: maestro test tests/smoke/.maestro/[flow].yaml
Detox: detox test --configuration ios.sim.debug --testNamePattern smoke
XCUITest: xcodebuild test -only-testing:UITests/SmokeUITests
Espresso: ./gradlew connectedAndroidTest -PtestFilter=SmokeTest

Read the full file on GitHub · 198 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.

6d ago First seen · 198 lines · 52 tokens per session scan A e7acef822fb9

Subscribe to this mod's changes

smoke-check is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 1,508 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 Mobile Testing

android-ui-journey-testing

XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.

sickn33/agentic-awesome-skills · 27 tokens

android_ui_verification

Automated end-to-end UI testing and verification on an Android Emulator using ADB.

sickn33/agentic-awesome-skills · 22 tokens

solopi-ai

A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.

alipay/SoloPi · 127 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

eas-simulator

EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…

expo/skills · 249 tokens

flutter-add-integration-test

Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests. Use when adding integration testing to a project, exploring UI components via MCP, or automating user flows with the integrationtest package.

flutter/agent-plugins · 48 tokens