A command for building an iOS or SwiftUI app, opening it in Apple’s device simulator, and visually checking its screens and user flows. It can also test empty, loading, and error states and take screenshots.

Use it to check a chosen screen or flow, select a simulator and Xcode scheme, capture each step, and optionally measure memory use and look for leaks.

It helps find visible problems and crashes without requiring you to write separate UI test code.

ios-test — Command for Claude Code by yusufkaran

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.

Clone the repo

git clone --depth 1 https://github.com/yusufkaran/swiftui-autotest-skill

Made for: Claude Code.

Or install swiftui-autotest-skill, the plugin that ships this one along with the rest of its 3 skills, 2 commands.

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/commands/yusufkaran/swiftui-autotest-skill/ios-test.svg)](https://agentmods.dev/commands/yusufkaran/swiftui-autotest-skill/ios-test)

Your own site

<a href="https://agentmods.dev/commands/yusufkaran/swiftui-autotest-skill/ios-test"><img src="https://agentmods.dev/badge/commands/yusufkaran/swiftui-autotest-skill/ios-test.svg" alt="Measured on agentmods" height="20"></a>

Per session 71 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,519 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.00071	$0.03519
Opus 5	$0.00036	$0.01759
Sonnet 5	$0.00014	$0.00704
Haiku 4.5	$0.00007	$0.00352

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

Security

Grade A, and why

ios-test 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 8d 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.

commands/ios-test.md · 344 lines

How it starts

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

Claude Command: iOS Test

Bu komut iOS/SwiftUI uygulamasini derleyip simulator'da acarak computer use ile gorsel test yapar.

Usage

/ios-test
/ios-test --flow=onboarding
/ios-test --screen=LoginView
/ios-test --device="iPhone 16 Pro"
/ios-test --scheme=MyApp
/ios-test --states
/ios-test --screenshot-all
/ios-test --flow=checkout --states --screenshot-all

Command Options

--flow=<name>: Belirli bir kullanici akisini test et (ornegin: onboarding, login, checkout)
--screen=<ViewName>: Sadece belirli bir ekrani test et
--device=<name>: Simulator cihazi belirt (ornegin: "iPhone 16 Pro", "iPhone SE")
--scheme=<name>: Xcode scheme belirt
--states: Empty, error ve loading state'lerini launch argument'lari ile test et
--screenshot-all: Her adimda screenshot al
--performance: Her ekranda RAM olcumu ve memory leak kontrolu yap (varsayilan testte YAPILMAZ)

What This Command Does

Phase 1: Project Discovery

Calisma dizininde .xcodeproj veya .xcworkspace dosyasini bul
- .xcworkspace varsa onu tercih et (CocoaPods/SPM workspace)
- Birden fazla varsa kullaniciya sor
- Hicbiri yoksa hata ver ve dur
Mevcut scheme'leri listele:
```
xcodebuild -list -workspace MyApp.xcworkspace
```
- --scheme verilmisse onu kullan
- Verilmemisse ve tek scheme varsa onu kullan
- Birden fazla varsa kullaniciya sor

Phase 2: Simulator Selection

ONEMLI: Simulator secimi build'den once yapilmalidir. Build komutu secilen cihaz ismini kullanir.

--device argumani verildiyse:
- O cihazi bul: xcrun simctl list devices --json
- Bulamazsa mevcut cihazlari listele ve kullaniciya sor
--device verilmediyse:
```
xcrun simctl list devices booted --json
```
- Hic booted simulator yoksa: Mevcut cihazlari listele:
```
xcrun simctl list devices available --json
```
  En uygun iPhone'u oner, kullaniciya "Bu cihazda test koşayım mı?" diye sor. Onaylarsa boot et:
```
xcrun simctl boot <device-udid>
open -a Simulator
```

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

8d ago First seen · 344 lines · 0 tokens per session scan A 1b442e7c8684

Subscribe to this mod's changes

ios-test is a command published in the GitHub repository yusufkaran/swiftui-autotest-skill (24 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 3,519 once invoked, about $0.0004 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-08-30.

Claude Code E2E testing Mobile Testing accessibility claude-code-plugin computer-use ios skills

test-simulator

Launch simulator testing agent for test scenarios and visual verification.

Kasempiternal/axiom-v2 · 14 tokens

feature-build

Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.

ahmed3elshaer/everything-claude-code-mobile · 45 tokens

feature-test

Create all tests for an implemented feature - unit tests (ViewModel, UseCase, Repository), Compose UI tests, and E2E user flow tests.

ahmed3elshaer/everything-claude-code-mobile · 31 tokens

feature-verify

Run final verification - pass@k test metrics, coverage report, and sign-off. Confirms feature is production-ready.

ahmed3elshaer/everything-claude-code-mobile · 24 tokens

mobile-app-testing

Read .cursor/playwright-skills/mobile-app-testing/SKILL.md and follow its instructions exactly. Treat that file's body as your operating instructions for this task. Template files to install live in .cursor/playwright-skills/mobile-app-testing/templates/.

FaisalNoman/playwright-skills · 0 tokens

dd-test-case

Generate Maestro test cases from test spec.

mkhrdev/cc-spec-driven · 7 tokens