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 skills/xvirobotics/metaskill/run-simulatornpx skills add xvirobotics/metaskill --skill run-simulatorgit clone --depth 1 https://github.com/xvirobotics/metaskillWrote 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/xvirobotics/metaskill/run-simulator)<a href="https://agentmods.dev/skills/xvirobotics/metaskill/run-simulator"><img src="https://agentmods.dev/badge/skills/xvirobotics/metaskill/run-simulator.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.00034 | $0.00895 |
| Opus 5 | $0.00017 | $0.00447 |
| Sonnet 5 | $0.00007 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
run-simulator 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- run-simulator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an iOS Simulator launch specialist. Your job is to build the app and run it in the iOS Simulator so the user can interact with it.
Instructions
Step 1: List Available Simulators
Find available iOS simulators:
xcrun simctl list devices available --json | python3 -c "
import json, sys
data = json.load(sys.stdin)
for runtime, devices in data.get('devices', {}).items():
if 'iOS' in runtime:
for d in devices:
if d.get('isAvailable'):
print(f\"{d['name']}|{d['udid']}|{runtime.split('.')[-1]}|{d['state']}\")
" 2>/dev/null
Step 2: Select the Best Simulator
Priority order for simulator selection:
- iPhone 16 Pro (latest flagship)
- iPhone 15 Pro
- iPhone 15
- Any available iPhone simulator with the latest iOS runtime
- If no iPhone is available, use iPad Pro
Store the selected device name and UDID.
Step 3: Boot the Simulator (if needed)
Check if the simulator is already booted. If not, boot it:
xcrun simctl boot <UDID> 2>/dev/null || true
Open the Simulator app so the user can see it:
open -a Simulator
Wait briefly for the simulator to finish booting:
xcrun simctl bootstatus <UDID> -b 2>/dev/null || sleep 3
Step 4: Locate the Xcode Project
Find the .xcworkspace or .xcodeproj:
find . -maxdepth 3 -name "*.xcworkspace" -not -path "*/Pods/*" | head -1
find . -maxdepth 3 -name "*.xcodeproj" | head -1
List schemes to find the main app scheme:
xcodebuild -list -workspace <workspace> 2>/dev/null || xcodebuild -list -project <project>
Step 5: Build and Install
Build the app for the simulator:
xcodebuild build \
-workspace <workspace-or-project> \
-scheme <app-scheme> \
-destination "platform=iOS Simulator,id=<UDID>" \
-derivedDataPath ./DerivedData \
-quiet \
2>&1
If the build fails, report the errors and stop.
Find the built .app bundle:
find ./DerivedData -name "*.app" -path "*/Build/Products/Debug-iphonesimulator/*" | head -1
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 · 134 lines · 34 tokens per session scan A eee62abbf5be
run-simulator is a skill published in the GitHub repository xvirobotics/metaskill (67 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 895 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 skills, from other repositories
suede-aso
Suede-owned app-store optimization discipline for keyword fields, titles, subtitles, descriptions, screenshots, ratings context, and competitor listing audits. Use when improving App Store or Google Play visibility or listing conversion from a live app URL and current console evidence. NOT FOR: building or releasing…
android-app-factory
Suede Labs Android app factory: plan, build, test, and release a production-grade native Android app from a product idea through Google Play. Use for requests to create, ship, submit, monetize, or modernize an Android app. Covers Kotlin and Jetpack Compose architecture, API-level policy verification, accessibility…
site-to-ios-app
Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Use when the user has a live site or web app and asks to put it on the App Store, wrap it in an app, ship an iOS version, or convert a PWA to native — covers URL audit, shell-vs-native strategy, App Store 4.2 wrapper risk…
run-simulator
Build and launch the app in the iOS Simulator. Automatically selects an appropriate simulator device, boots it if needed, and installs and launches the app.
kotlin-specialist
Provides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction, Ktor server setup, and type-safe DSL design. Use when building Kotlin applications requiring coroutines, multiplatform development, or Android with Compose.…
swiftui-dev
Use this skill for SwiftUI development, architecture, structure, performance, and Apple native app profiling. It combines.