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 Xopoko/build-swift-apps --skill ios-rocketsim-operatorgit clone --depth 1 https://github.com/Xopoko/build-swift-appsWrote 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/xopoko/build-swift-apps/ios-rocketsim-operator)<a href="https://agentmods.dev/skills/xopoko/build-swift-apps/ios-rocketsim-operator"><img src="https://agentmods.dev/badge/skills/xopoko/build-swift-apps/ios-rocketsim-operator/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/xopoko/build-swift-apps/ios-rocketsim-operator"><img src="https://agentmods.dev/badge/skills/xopoko/build-swift-apps/ios-rocketsim-operator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00566 |
| Opus 5 | $0.00015 | $0.00283 |
| Sonnet 5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
ios-rocketsim-operator 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 12d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS RocketSim Operator
Before invoking Apple-only binaries, confirm the execution context is macOS. From Windows or Linux, run those steps in a Mac SSH project or through an already configured remote transport; do not retry missing Apple binaries locally.
Use the installed RocketSim app as the versioned Simulator automation layer. Always resolve the matching app bundle, bundled skill, and CLI before interacting with a simulator.
Discovery
Prefer a running RocketSim bundle:
ROCKETSIM_PID="$(pgrep -x RocketSim | head -1)"
APP_PATH=""
if [ -n "$ROCKETSIM_PID" ]; then
APP_PATH="$(ps -o command= -p "$ROCKETSIM_PID" | sed 's#/Contents/MacOS/RocketSim$##')"
fi
printf '%s\n' "$APP_PATH"
If not running, enumerate candidates with:
mdfind "kMDItemCFBundleIdentifier == 'com.swiftLee.RocketSim'"
Also check /Applications/RocketSim.app, /Applications/RocketSim 2.app, ~/Applications/RocketSim.app, and ~/Applications/RocketSim 2.app.
For each candidate, validate both files:
test -f "$APP_PATH/Contents/Resources/Agent-Skill/SKILL.md" && \
test -x "$APP_PATH/Contents/Helpers/rocketsim"
Use the first valid candidate. If RocketSim is running, use the running bundle only if it validates; otherwise rediscover or stop.
If no candidate validates, tell the user to launch or install a current RocketSim build from the Mac App Store:
https://apps.apple.com/us/app/rocketsim-for-xcode-simulator/id1504940162
Required Paths
After discovery, set:
- Bundled skill:
$APP_PATH/Contents/Resources/Agent-Skill/SKILL.md - CLI:
$APP_PATH/Contents/Helpers/rocketsim
Before any CLI call:
pgrep -x RocketSim >/dev/null && echo "Running" || echo "Not running"
If RocketSim is not running, ask the user to launch it. If it is running from a different bundle than APP_PATH, restart discovery and prefer the running bundle.
Handoff
Read the bundled Agent-Skill/SKILL.md and follow it. Wherever it refers to rocketsim, use the resolved absolute CLI path. Do not use ad hoc simulator automation until discovery, validation, and the running-app check pass.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 63 lines · 31 tokens per session scan A e1ad8ceb1c99
ios-rocketsim-operator is a skill published in the GitHub repository Xopoko/build-swift-apps (45 stars, last pushed 15d ago), licensed MIT. It adds 31 tokens to every session and 566 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
e2e-testing
AI-powered E2E testing for any app — Flutter, React Native, iOS, Android, Electron, Tauri, KMP, .NET MAUI. Connects via MCP to running apps so the agent can take screenshots, tap elements, enter text, scroll, inspect UI trees, and verify state with natural language. Use when the user wants to test an app's UI…
Appium Mobile Testing
Mobile application testing skill using Appium for iOS and Android, covering device capabilities, selectors, gestures, and cross-platform testing strategies.
Espresso Android Testing
Android UI testing with Espresso framework including view matchers, actions, assertions, idling resources, and RecyclerView testing patterns.
cometchat-android-v6-testing
Test an Android app that integrates the CometChat v6 UI Kit — make the SDK mockable behind a repository, unit-test the init/login gate and credential hygiene, write instrumented/Compose UI tests for chat screens, and know honestly what can only be checked on a device. Triggers: 'how do I test my cometchat android…
cometchat-flutter-v6-testing
Test a Flutter app that uses the CometChat UI Kit — what is worth testing versus what belongs to the kit, mocking the SDK boundary, widget tests around chat screens, and integration/CI setup. Triggers: 'test my cometchat integration', 'mock cometchat in flutter tests', 'widget test chat screen', 'cometchat test setup'.
cometchat-react-native-testing
Test a CometChat React Native integration — mock the SDK for Jest unit tests, assert init-before-render ordering and no-Auth-Key-in-source, and use Detox for the flows only a device can prove. Triggers: test CometChat React Native, mock CometChat SDK jest, detox CometChat, unit test chat screen RN, CI tests for chat.