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 yusufkaran/swiftui-autotest-skill --skill ios-testgit clone --depth 1 https://github.com/yusufkaran/swiftui-autotest-skillWrote 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/yusufkaran/swiftui-autotest-skill/ios-test)<a href="https://agentmods.dev/skills/yusufkaran/swiftui-autotest-skill/ios-test"><img src="https://agentmods.dev/badge/skills/yusufkaran/swiftui-autotest-skill/ios-test/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/yusufkaran/swiftui-autotest-skill/ios-test"><img src="https://agentmods.dev/badge/skills/yusufkaran/swiftui-autotest-skill/ios-test.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.00069 | $0.02544 |
| Opus 5 | $0.00034 | $0.01272 |
| Sonnet 5 | $0.00014 | $0.00509 |
| Haiku 4.5 | $0.00007 | $0.00254 |
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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Test Skill
Overview
Use this skill to build an iOS/SwiftUI application, launch it in the Simulator, and visually test it using computer use. The skill navigates through every screen, screenshots each state, checks crash logs, and produces a structured test report — without writing a single line of test code.
Options
--flow=<name>: Test a specific user flow (e.g., onboarding, login, checkout)--screen=<ViewName>: Test only a specific screen--device=<name>: Choose a Simulator device (e.g., "iPhone 16", "iPhone SE")--scheme=<name>: Specify the Xcode scheme--states: Test empty, error, and loading states via launch arguments--screenshot-all: Screenshot every step--performance: Measure RAM per screen and check for memory leaks (skipped by default)
Workflow
1) Project Discovery
- Find
.xcodeprojor.xcworkspacein the working directory- Prefer
.xcworkspaceif it exists (CocoaPods/SPM workspace) - If multiple exist, ask the user which one to use
- If none found, stop with an error
- Prefer
- List available schemes:
xcodebuild -list -workspace MyApp.xcworkspace- Use
--schemeif provided - If only one scheme exists, use it automatically
- If multiple, ask the user
- Use
2) Simulator Selection (BEFORE build)
IMPORTANT: Simulator must be selected BEFORE building. The build command uses the selected device name.
- If
--deviceis provided: find that device viaxcrun simctl list devices --json - If
--deviceis not provided, check booted simulators:xcrun simctl list devices booted --json- No booted simulator: list available devices with
xcrun simctl list devices available --json, suggest the best iPhone match, ask for confirmation, then boot it - One booted simulator: use it directly, no questions
- Multiple booted: list them and ask the user which one to use
- No booted simulator: list available devices with
3) Accessibility Check (MANDATORY — DO NOT SKIP)
This step is MANDATORY. Runs BEFORE build. NEVER skip this step.
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.
- 9d ago First seen · 293 lines · 69 tokens per session scan A f56e6c566d7c
ios-test is a skill published in the GitHub repository yusufkaran/swiftui-autotest-skill (24 stars, last pushed 5mo ago), licensed MIT. It adds 69 tokens to every session and 2,544 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-08-30.
Other skills, from other repositories
ui-crawler-max
Autonomous UI crawler for iOS simulator apps — rapid, element-precise data collection. Use whenever the user says "crawl my app", "auto-test the UI", "click/tap through every screen", "monkey test", "explore the app and find errors/crashes", "collect screenshots of all screens", "smoke test the whole app", or asks for…
iOS Testing
XCTest unit tests, XCUITest UI tests, snapshot testing, and performance baselines for iOS apps.
aco
Drive a live Appium session from the shell with the aco CLI. Use when the user wants to interact with a running mobile app on an iOS simulator, Android emulator, or connected real device — tap, swipe, type, screenshot, read the screen/page source, find UI elements, switch to a WebView context, or call iOS/Android…
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
baguette
Drive iOS simulators programmatically via the baguette CLI — taps, swipes, multi-finger gestures, hardware buttons (Home / Lock / Volume / Action / Power), ASCII keyboard text, and frame capture, all without opening Xcode. Use when: (1) an agent needs to drive a booted iOS simulator from a script — tap a coordinate…