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 agentmods add commands/okminlee/everything-claude-code-ios/xcuitestgit clone --depth 1 https://github.com/OkminLee/everything-claude-code-iosWrote 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/commands/okminlee/everything-claude-code-ios/xcuitest)<a href="https://agentmods.dev/commands/okminlee/everything-claude-code-ios/xcuitest"><img src="https://agentmods.dev/badge/commands/okminlee/everything-claude-code-ios/xcuitest.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.02705 |
| Opus 5 | $0.00016 | $0.01352 |
| Sonnet 5 | $0.00006 | $0.00541 |
| Haiku 4.5 | $0.00003 | $0.00270 |
Grade A, and why
xcuitest 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 4d 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XCUITest Command
This command invokes the xcuitest-runner agent to generate, maintain, and execute end-to-end UI tests for iOS apps.
What This Command Does
- Generate Test Journeys - Create XCUITest tests for user flows
- Run UI Tests - Execute tests on simulators/devices
- Capture Artifacts - Screenshots, videos on failures
- Manage Flaky Tests - Quarantine unstable tests
- Generate Reports - xcresult bundles for analysis
When to Use
Use /xcuitest when:
- Testing critical user journeys (login, onboarding, payments)
- Verifying multi-step flows work end-to-end
- Testing UI interactions and navigation
- Validating accessibility
- Preparing for App Store submission
- Testing push notification handling
How It Works
The xcuitest-runner agent will:
- Analyze user flow and identify test scenarios
- Generate XCUITest using Page Object Model (Screen Objects)
- Set up accessibility identifiers if missing
- Run tests on specified simulators
- Capture failures with screenshots and videos
- Generate report with results and artifacts
Example Usage
User: /xcuitest Test the login and home flow
Agent (xcuitest-runner):
# E2E Test Generation: Login to Home Flow
## Test Scenario Identified
**User Journey:** Launch → Login → Home Screen
**Test Coverage:**
1. App launches successfully
2. Login screen appears
3. Enter credentials
4. Tap login button
5. Home screen loads
6. User name displayed
## Generated Screen Objects
```swift
// UITests/Screens/LoginScreen.swift
import XCTest
final class LoginScreen {
private let app: XCUIApplication
init(app: XCUIApplication) {
self.app = app
}
// MARK: - Elements
var emailField: XCUIElement { app.textFields["email-field"] }
var passwordField: XCUIElement { app.secureTextFields["password-field"] }
var loginButton: XCUIElement { app.buttons["login-button"] }
var errorLabel: XCUIElement { app.staticTexts["error-label"] }
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.
- 4d ago First seen · 439 lines · 32 tokens per session scan A 710d10ca948e
xcuitest is a command published in the GitHub repository OkminLee/everything-claude-code-ios (58 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 2,705 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-08-30.
Other commands, from other repositories
test-simulator
Launch simulator testing agent for test scenarios and visual verification.
run-tests
Run XCUITests and parse results using the test-runner agent.
qa-ios-screenshot
Take a simulator screenshot and analyze it for visual issues.
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/.
test-xcode
Build and test iOS apps on simulator using XcodeBuildMCP.
test-xcode
Build and test iOS apps on simulator using XcodeBuildMCP.