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 jeffy-w/AgentSkills --skill ios-device-build-rungit clone --depth 1 https://github.com/jeffy-w/AgentSkillsWrote 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/jeffy-w/agentskills/ios-device-build-run)<a href="https://agentmods.dev/skills/jeffy-w/agentskills/ios-device-build-run"><img src="https://agentmods.dev/badge/skills/jeffy-w/agentskills/ios-device-build-run/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/jeffy-w/agentskills/ios-device-build-run"><img src="https://agentmods.dev/badge/skills/jeffy-w/agentskills/ios-device-build-run.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.00085 | $0.01889 |
| Opus 5 | $0.00043 | $0.00945 |
| Sonnet 5 | $0.00017 | $0.00378 |
| Haiku 4.5 | $0.00009 | $0.00189 |
Grade A, and why
ios-device-build-run 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Device Build Run
Use the bundled script for repeatable real-device build/run/log workflows:
python3 ios-device-build-run/scripts/ios_device_build_run.py <subcommand> [options]
The script stores durable sessions under:
~/.codex/ios-device-build-run/sessions/<timestamp>-<scheme>/
Each session may contain build.raw.log, build.pretty.log, install.log, run.log, device.log, metadata.json, events.jsonl, pids.json, and devicectl JSON outputs.
Workflow
- Run
doctorif the environment is unknown:python3 ios-device-build-run/scripts/ios_device_build_run.py doctor - Prefer
build-runfor the normal path:python3 ios-device-build-run/scripts/ios_device_build_run.py build-run - Device auto-selection prefers wired USB devices. If exactly one wired device is connected, it is used automatically; otherwise pass
--device <udid-or-name>. - Read logs through the script instead of dumping whole files:
python3 ios-device-build-run/scripts/ios_device_build_run.py logs --session latest --file build --tail 200 python3 ios-device-build-run/scripts/ios_device_build_run.py logs --session latest --file device --grep EffectEngine --tail 300 python3 ios-device-build-run/scripts/ios_device_build_run.py logs --session latest --file all --search 'error|fatal|crash' --ignore-case --context 3 - Stop background runtime logging when done:
python3 ios-device-build-run/scripts/ios_device_build_run.py stop-log --session latest
Subcommands
doctor: verifyxcodebuild,xcrun, optionalidevicesyslog, optionalxcbeautify, and connected physical devices.devices: list available physical iOS devices; simulators are excluded.build: build only, create a session, locate the.app, and readCFBundleIdentifierfromInfo.plist.install: install an existing or latest-session.apponto a physical device.run: launch an already-installed app from a session or explicit--bundle-id.build-run: build, locate app, install, start runtime log stream, then launch.log-stream: start only runtime log capture for a session.logs: filter/search/tail persisted logs.stop-log: terminate the background runtime log process recorded inpids.json.sessions: list recent sessions.
What ships with it
2 files 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.
- 9d ago First seen · 155 lines · 85 tokens per session scan A f8ea6a52254f
ios-device-build-run is a skill published in the GitHub repository jeffy-w/AgentSkills (2 stars, last pushed 3mo ago), licensed MIT. It adds 85 tokens to every session and 1,889 once invoked, about $0.0004 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-31.
Other skills, from other repositories
orca-emulator-android
Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.