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/moasq/ios-dev-agent/crashnpx skills add moasq/ios-dev-agent --skill crashgit clone --depth 1 https://github.com/moasq/ios-dev-agentWhat 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.00047 | $0.01555 |
| Opus 5 | $0.00023 | $0.00777 |
| Sonnet 5 | $0.00009 | $0.00311 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
crash 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 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.
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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runtime Crash Investigation
Automated crash detection and resolution for iOS apps.
Quick Start
When the user reports a crash ("the app crashes when...") or you need to verify stability:
- Run the smoke walker test — this walks every screen automatically
- If test fails — you have the exact crash point, skip to Step 4
- If test passes — the crash is flow-specific, investigate manually
Step 1: Run Automated Smoke Tests
Use Xcode MCP to run the smoke walker:
mcp__xcode__RunSomeTests with:
targetName: "<AppName>UITests"
testIdentifier: "SmokeWalkerTest"
Or run a specific test if you suspect a particular flow:
SmokeWalkerTest/testFullLoggingFlow— full 4-step loggingSmokeWalkerTest/testQuickSaveFlow— quick save from severitySmokeWalkerTest/testStepNavigation— back/forward between stepsSmokeWalkerTest/testMigraineDetailAndEdit— detail view + edit mode
If the smoke walker test target doesn't exist yet, see the Setup section below.
Step 2: Parse Test Results
If a test fails, the Xcode MCP response includes:
- Which test method failed — tells you which screen/flow crashed
- The assertion message — tells you what was expected vs what happened
- If it's a crash — no assertion, the app terminated unexpectedly
Map the failing test to the screen:
| Test Method | Screen | Flow |
|---|---|---|
testHomeScreenLoads |
Home | App launch |
testFullLoggingFlow |
LogAttackSheet | Step-by-step logging |
testQuickSaveFlow |
LogAttackSheet | Quick save from step 1 |
testStepNavigation |
LogAttackSheet | Forward/back navigation |
testDismissLogSheet |
LogAttackSheet | Sheet dismiss |
testSettingsOpens |
SettingsSheet | Settings display |
testHistoryOpens |
HistoryView | History display |
testMigraineDetailAndEdit |
MigraineDetailSheet | Detail + edit |
Step 3: Harvest Crash Logs
After a test crash, check for crash logs:
find ~/Library/Logs/DiagnosticReports -name "*<AppName>*" -newer /tmp/.last_test_run -type f 2>/dev/null | head -5
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 · 185 lines · 47 tokens per session scan A 2b756048eb03
crash is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,555 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-31.
Other skills, from other repositories
edge-to-edge
Use this skill to migrate your Jetpack Compose app to add adaptive edge-to-edge support and troubleshoot common issues. Use this skill to fix UI components (like buttons or lists) that are obscured by or overlapping with the navigation bar or status bar, fix IME insets, and fix system bar legibility.
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.
flutter-fix-layout-issues
Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. Use when addressing "RenderFlex overflowed", "Vertical viewport was given unbounded height", or similar layout issues.
referral-program
When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…