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/debuggingnpx skills add moasq/ios-dev-agent --skill debugginggit 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.00049 | $0.02243 |
| Opus 5 | $0.00024 | $0.01122 |
| Sonnet 5 | $0.00010 | $0.00449 |
| Haiku 4.5 | $0.00005 | $0.00224 |
Grade A, and why
debugging 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 yesterday.
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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Debugging & Crash Investigation
Use this guide when diagnosing runtime crashes, render errors, or unexpected behavior.
MCP Tool Selection — Check What's Available
At the start of a debugging session, check which MCP servers are loaded. Use ToolSearch to probe:
ToolSearch("XcodeBuildMCP") → if found: full LLDB + simulator + build
ToolSearch("mcp__xcode__") → if found: build + preview + test (no LLDB)
Priority order:
- Apple Xcode MCP (
mcp__xcode__*) — use for build, preview, test, issues, build log - XcodeBuildMCP (
mcp__XcodeBuildMCP__*) — use ONLY for what Apple Xcode MCP cannot do: LLDB debugging, simulator log capture, screenshots, UI snapshots, video recording
What Apple Xcode MCP handles (prefer these when available):
| Capability | Tool |
|---|---|
| Build | mcp__xcode__BuildProject |
| Preview | mcp__xcode__RenderPreview |
| Run tests | mcp__xcode__RunSomeTests / RunAllTests |
| Navigator issues | mcp__xcode__XcodeListNavigatorIssues |
| Build log | mcp__xcode__GetBuildLog |
| Read files | mcp__xcode__XcodeRead |
| Search code | mcp__xcode__XcodeGrep |
| Find files | mcp__xcode__XcodeGlob |
| Code diagnostics | mcp__xcode__XcodeRefreshCodeIssuesInFile |
| Execute snippet | mcp__xcode__ExecuteSnippet |
What ONLY XcodeBuildMCP can do (fallback to these):
| Capability | Tool |
|---|---|
| LLDB attach | mcp__XcodeBuildMCP__debugging__attach |
| Backtrace | mcp__XcodeBuildMCP__debugging__stack |
| Frame variables | mcp__XcodeBuildMCP__debugging__variables |
| Run LLDB command | mcp__XcodeBuildMCP__debugging__lldb_command |
| Add breakpoint | mcp__XcodeBuildMCP__debugging__add_breakpoint |
| Remove breakpoint | mcp__XcodeBuildMCP__debugging__remove_breakpoint |
| Continue execution | mcp__XcodeBuildMCP__debugging__continue |
| Detach debugger | mcp__XcodeBuildMCP__debugging__detach |
| Simulator log capture | mcp__XcodeBuildMCP__simulator__start_simulator_log_capture / stop_simulator_log_capture |
| Launch with logs | mcp__XcodeBuildMCP__simulator__launch_app_with_logs |
| Screenshot | mcp__XcodeBuildMCP__simulator__screenshot |
| UI hierarchy snapshot | mcp__XcodeBuildMCP__simulator__snapshot_ui |
| Record video | mcp__XcodeBuildMCP__simulator__record_video |
| Build & run (sim) | mcp__XcodeBuildMCP__simulator__build_and_run |
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.
- yesterday First seen · 188 lines · 49 tokens per session scan A 1d8821d1db77
debugging is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 2,243 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…