Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/markdavidgan/apple-dev-skillsnpx agentmods add skills/markdavidgan/apple-dev-skills/ios-simulateWrote 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/markdavidgan/apple-dev-skills/ios-simulate)<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/ios-simulate"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/ios-simulate.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.1 | $0.00096 | $0.04187 |
| Opus 5 | $0.00048 | $0.02093 |
| Sonnet 5 | $0.00019 | $0.00837 |
| Haiku 4.5 | $0.00010 | $0.00419 |
Grade A, and why
ios-simulate 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 5d 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 — 714 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Simulate
iOS Simulator management, screenshot automation, and device control via xcrun simctl. Use for testing, screenshots, and simulator-based workflows.
Quick Reference
| Task | Command |
|---|---|
| List devices | xcrun simctl list devices available |
| Boot simulator | xcrun simctl boot "iPhone 17 Pro Max" |
| Screenshot | xcrun simctl io booted screenshot output.png |
| Record video | xcrun simctl io booted recordVideo output.mp4 |
| Install app | xcrun simctl install booted MyApp.app |
| Uninstall app | xcrun simctl uninstall booted com.example.app |
| Set dark mode | xcrun simctl ui booted appearance dark |
| Open URL | xcrun simctl openurl booted https://example.com |
Simulator Management
List Available Simulators
# All devices (including unavailable)
xcrun simctl list devices
# Only available devices
xcrun simctl list devices available
# JSON output (for scripting)
xcrun simctl list devices available -j
# Filter by device type
xcrun simctl list devices | grep "iPhone"
Boot and Shutdown
# Boot a specific device by name
xcrun simctl boot "iPhone 17 Pro Max"
# Boot by UDID
xcrun simctl boot 4C6DD567-0C7E-476D-8946-8CA9A21A9452
# Wait for boot to complete
xcrun simctl bootstatus "iPhone 17 Pro Max" -b
# Shutdown
xcrun simctl shutdown "iPhone 17 Pro Max"
# Shutdown all simulators
xcrun simctl shutdown all
# Check if running
xcrun simctl list devices | grep "iPhone 17 Pro Max" | grep "Booted"
Create Custom Simulators
# List available device types
xcrun simctl list devicetypes
# List available runtimes
xcrun simctl list runtimes
# Create custom simulator
xcrun simctl create "My iPhone 15" "iPhone 15" "iOS17.4"
# Delete simulator
xcrun simctl delete "My iPhone 15"
# Erase all content and settings
xcrun simctl erase "iPhone 17 Pro Max"
Open Simulator App
# Open Simulator.app
open -a Simulator
# Open with specific device
xcrun simctl boot "iPhone 17 Pro Max" && open -a Simulator
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.
- 5d ago First seen · 714 lines · 96 tokens per session scan A 2a809365fe9e
ios-simulate is a skill published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 9d ago), licensed MIT. It adds 96 tokens to every session and 4,187 once invoked, about $0.0005 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.
Other skills, from other repositories
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…
asc-revenuecat-catalog-sync
Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.
asc-localize-metadata
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
asc-release-flow
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and…
asc-submission-health
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and…