A one-time setup tool for a mobile app's tests and continuous integration (CI), which automatically runs checks when code changes. It creates test folders, sample tests, a test runner, and a GitHub Actions or Bitrise workflow.

Use it during technical setup to prepare mobile test directories, choose a framework-specific test stack, add runnable examples, and configure automated test runs.

It removes the need to manually organize the test pyramid—the layers of unit, component, and end-to-end tests—or write the CI configuration before development starts.

test-setup — 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 test-setup

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

Your own site

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/test-setup"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/test-setup/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/test-setup"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/test-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,842 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.00047	$0.01842
Opus 5	$0.00023	$0.00921
Sonnet 5	$0.00009	$0.00368
Haiku 4.5	$0.00005	$0.00184

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

Security

Grade A, and why

test-setup 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/test-setup/SKILL.md · 231 lines

How it starts

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

Test Setup

One-shot scaffolding of a mobile project's test pyramid plus its CI runner. Reads the pinned framework, generates the test directory tree, drops in a runnable example test for each level, and writes a CI workflow file that invokes the right runner.

Phase 1: Read Project Context

Read these in parallel:

CLAUDE.md — confirm project name and target platforms.
.claude/docs/technical-preferences.md — pull Framework, Language, Naming Conventions, Testing Framework (if already chosen), and Target Platforms.
.claude/docs/coding-standards.md — confirm the test naming and determinism rules.

If Framework is [TO BE CONFIGURED], stop and tell the user: "Run /setup-framework first; the test scaffolding depends on a pinned framework."

Phase 2: Pick the Test Stack

If the Testing Framework field is empty, propose a default per framework via AskUserQuestion:

Framework	Unit	Component / widget	E2E
React Native	Jest + React Native Testing Library	RNTL	Detox or Maestro
Flutter	`package:test`	`flutter_test` widget tests	`integration_test` + Maestro or Patrol
iOS native	XCTest	XCTest + ViewInspector (SwiftUI)	XCUITest or Maestro
Android native	JUnit5 + MockK	Compose UI test or Espresso	Espresso, UI Automator, or Maestro

Confirm the choices with the user. Persist the answer back into .claude/docs/technical-preferences.md under ## Testing as Framework: [choices].

Phase 3: Choose the CI Provider

Parse the --ci flag. If absent, ask:

[A] GitHub Actions (default for OSS, free macOS minutes are limited)
[B] Bitrise (mobile-first, simpler iOS signing)
[C] CircleCI
[D] None — local only for now

Capture the choice in technical-preferences as CI: [provider].

Phase 4: Create the Directory Tree

Confirm with the user:

"I'd like to create the following:

tests/
  unit/                 — fast, deterministic, no I/O
  integration/          — multi-module, may use in-memory DB
  e2e/                  — full app on simulator/emulator
  helpers/              — factories, mocks, shared assertions
  fixtures/             — JSON / image fixtures
  regression/           — bug regression tests
  smoke/                — critical-path smoke tests
Plus a runner config file and a CI workflow.
May I proceed?"

Read the full file on GitHub · 231 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 · 231 lines · 47 tokens per session scan A b16660637b25

Subscribe to this mod's changes

test-setup is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,842 once invoked, about $0.0002 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.

DevOps and cloud E2E testing Testing Unit testing

axiom-testing

Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.

CharlesWiltgen/Axiom · 38 tokens

designing-tests

Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.

CloudAI-X/claude-workflow-v2 · 48 tokens

test-automation

Execute Vitest and Playwright test suites with result collection and failure analysis.

a5c-ai/babysitter · 0 tokens

testing-blocks

Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.

adobe/skills · 61 tokens

prd-auto-test-loop

A testing workflow driven by a product requirements document (PRD), which describes what a software version should do. It turns acceptance criteria into unit, integration, and end-to-end tests, then records the plan and results.

yunshu0909/yunshu_skillshub · 79 tokens

test-automation-expert

Comprehensive test automation specialist covering unit, integration, and E2E testing strategies. Expert in Jest, Vitest, Playwright, Cypress, pytest, and modern testing frameworks. Guides test pyramid design, coverage optimization, flaky test detection, and CI/CD integration. Activate on 'test strategy', 'unit tests'…

curiositech/some_claude_skills · 133 tokens