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/aiocean/claude-plugins/aio-ios-device-debugnpx skills add aiocean/claude-plugins --skill aio-ios-device-debuggit clone --depth 1 https://github.com/aiocean/claude-pluginsWrote 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/aiocean/claude-plugins/aio-ios-device-debug)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-ios-device-debug"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-ios-device-debug.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.00157 | $0.02377 |
| Opus 5 | $0.00078 | $0.01189 |
| Sonnet 5 | $0.00031 | $0.00475 |
| Haiku 4.5 | $0.00016 | $0.00238 |
Grade B, and why
aio-ios-device-debug scanned grade B with 1 finding 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo python3 -m pymobiledevice3 remote tunneld -p tcp How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCRIPTS="${CLAUDE_PLUGIN_ROOT}/skills/aio-ios-device-debug/scripts"
iOS Device Debug
Environment
- xcode-select: !
xcode-select -p 2>/dev/null || echo "NOT INSTALLED" - idevicesyslog: !
which idevicesyslog 2>/dev/null || echo "NOT INSTALLED — brew install libimobiledevice" - idevicecrashreport: !
which idevicecrashreport 2>/dev/null || echo "NOT INSTALLED — brew install libimobiledevice" - python3: !
which python3 2>/dev/null || echo "NOT INSTALLED" - pymobiledevice3: !
python3 -c "import pymobiledevice3" 2>/dev/null && echo "installed" || echo "NOT INSTALLED — pip3 install pymobiledevice3" - Connected devices: !
idevice_id -l 2>/dev/null || echo "none detected (or idevice_id missing)"
Debug iOS apps on physical devices: build, install, launch, capture logs, pull crash reports, and analyze crashes — all from the terminal without Xcode GUI.
Prerequisites
Required tools (check before starting):
- Xcode with command line tools (
xcode-select --install) - libimobiledevice:
brew install libimobiledevice(providesidevicesyslog,idevicecrashreport) - pymobiledevice3:
pip3 install pymobiledevice3(required for screenshots on iOS 17+) - Python 3: for crash report parsing and pymobiledevice3
- Physical iOS device connected via USB or WiFi
Workflow Overview
The debug workflow follows this sequence:
- Discover device — find device ID
- Build & install — compile and deploy to device
- Launch & capture logs — run app while recording syslog
- Check for crash — search logs for Corpse/signal
- Pull crash reports — extract .ips files from device
- Analyze crash — parse .ips for stack trace and root cause
Scripts
| Script | Purpose |
|---|---|
$SCRIPTS/device-list.sh |
List connected devices with both devicectl and xcodebuild IDs |
$SCRIPTS/build-install.sh |
Build scheme and install on device |
$SCRIPTS/launch-and-log.sh |
Launch app, capture syslog, check for crashes |
$SCRIPTS/pull-crash-reports.sh |
Pull .ips crash reports from device |
$SCRIPTS/analyze-crash.sh |
Parse .ips file into human-readable analysis |
$SCRIPTS/screenshot.sh |
Capture screenshot from device (iOS 17+ compatible) |
What ships with it
7 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.
- 2d ago First seen · 213 lines · 157 tokens per session scan B 375a3496c613
aio-ios-device-debug is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 2d ago), licensed MIT. It adds 157 tokens to every session and 2,377 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
swiftui-dev
Use this skill for SwiftUI development, architecture, structure, performance, and Apple native app profiling. It combines.
flutter-mcp-toolkit-control
Drive a running Flutter app — tap, scroll, type, fill forms, hot-reload, navigate. Use when you need to interact with the UI.
flutter-mcp-toolkit-intentcall-migration
Migrate Flutter app code from removed MCPCallEntry to AgentCallEntry after the hard cut. Use when upgrading mcptoolkit, fixing compile errors after a major bump, or running flutter-mcp-toolkit migrate agent-entries.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.