crash-debugging

crash-debugging is a skill for Claude Code, Codex from conorluddy/xclaude-plugin. It costs 61 tokens per session (5,471 once invoked), scanned A, original, MIT.

A guide for investigating iOS app crashes from crash reports and logs. Symbolication uses a matching dSYM file to replace machine addresses in a stack trace with readable function names.

In plain words
What is it for?
Use it to retrieve simulator or device crash logs, symbolicate stack traces, locate dSYM files, identify common crash patterns, and investigate memory-related crashes.
Why use it?
It turns difficult-to-read crash data into clues about where and why an app failed.

Skill for Claude CodeCodex

Part of the xclaude-plugin plugin — 8 skills, 2 MCP servers shipped together

Install

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.

agentmods
npx agentmods add skills/conorluddy/xclaude-plugin/crash-debugging
Any agent
npx skills add conorluddy/xclaude-plugin --skill crash-debugging
Clone the repo
git clone --depth 1 https://github.com/conorluddy/xclaude-plugin

Made for: Claude Code, Codex.

Or install xclaude-plugin, the plugin that ships this one along with the rest of its 8 skills, 2 MCP servers.

Wrote 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.

agentmods badge for crash-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/conorluddy/xclaude-plugin/crash-debugging.svg)](https://agentmods.dev/skills/conorluddy/xclaude-plugin/crash-debugging)
Your own site
<a href="https://agentmods.dev/skills/conorluddy/xclaude-plugin/crash-debugging"><img src="https://agentmods.dev/badge/skills/conorluddy/xclaude-plugin/crash-debugging.svg" alt="Measured on agentmods" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,471 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00061 $0.05471
Opus 5 $0.00030 $0.02736
Sonnet 5 $0.00012 $0.01094
Haiku 4.5 $0.00006 $0.00547

Measured 4d ago against content hash b425f07e47b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

crash-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 4d 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.

skills/crash-debugging/SKILL.md · 908 lines

How it starts

The opening of the file, as written. The whole thing — 908 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Crash Debugging Skill

Comprehensive guide to iOS crash analysis and debugging

Quick Reference

Task Tool/Command Location
View crash logs Console.app macOS Application
Retrieve simulator crashes ~/Library/Logs/DiagnosticReports/ File system
Symbolicate crash atos Command line
Find dSYM files Xcode Organizer / DerivedData Xcode
Analyze crash type Stack trace patterns Crash log

Overview

Crash debugging transforms cryptic crash logs into actionable insights. This skill covers:

  • Retrieving crash logs from simulators and devices
  • Understanding crash log structure
  • Symbolicating stack traces for readable function names
  • Identifying common crash patterns
  • Determining root causes

When to Use This Skill

Use this skill when:

  • App crashes during testing or development
  • Received crash reports from users or TestFlight
  • CI/CD pipeline reports test crashes
  • Need to symbolicate production crash logs
  • Investigating memory issues or crashes

Don't use for:

  • Build failures (see xcode-workflows)
  • Test assertion failures (see ios-testing-patterns)
  • UI debugging (see ui-automation-workflows)

Key Concepts

Crash Logs vs Diagnostic Reports

Crash Logs:

  • Generated when app terminates unexpectedly
  • Include exception type, stack trace, register state
  • Stored in DiagnosticReports directory
  • Named: AppName_YYYY-MM-DD-HHMMSS_DeviceName.crash

Diagnostic Reports:

  • Broader category including crashes, spins, hangs
  • May include system diagnostics
  • Same location as crash logs

Symbolication Process

Unsymbolicated:

0   MyApp    0x0000000102a3c4f8 0x102a38000 + 17656
1   MyApp    0x0000000102a3d1a4 0x102a38000 + 20900

Symbolicated:

0   MyApp    0x0000000102a3c4f8 ViewController.loginButtonTapped() + 120
1   MyApp    0x0000000102a3d1a4 ViewController.viewDidLoad() + 84

Symbolication Requirements:

  1. dSYM file matching the build UUID
  2. Binary (MyApp.app/MyApp)
  3. Crash log with memory addresses

Read the full file on GitHub · 908 lines

Changes

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.

  1. 4d ago First seen · 908 lines · 61 tokens per session scan A b425f07e47b6

Subscribe to this mod's changes

crash-debugging is a skill published in the GitHub repository conorluddy/xclaude-plugin (182 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 5,471 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

platform-specialist

Doc-driven platform integration expert. Converts a web app to LINE MINI App (LIFF SDK), PWA (Next.js 16), and Capacitor (iOS/Android). Expo & Tauri are secondary/legacy. ปรัชญาหลัก: ดึง docs จริงล่าสุดก่อนเขียนโค้ดเสมอ — ไม่ freeze snippet ที่จะ rot. Triggers: "LINE MINI App", "LIFF", "LINE OA", "convert to app"…

wasintoh/toh-framework · 161 tokens

goga-cell-kotlin

Kotlin rules for implementing CODEMANIFEST contracts.

qarium/goga · 15 tokens

goga-cell-swift

Swift CODEMANIFEST contract implementation rules.

qarium/goga · 13 tokens

planflow

Draft a plan and get it approved as an editable flowchart in the user's browser before executing. Use when the user asks to plan a task with PlanFlow, or wants to review, edit, or approve a plan before any code changes are made.

davejj1530/planflow-greenlight · 53 tokens

skill-reviewer

Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.

bytedance/deer-flow · 38 tokens

surprise-me

Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for…

bytedance/deer-flow · 67 tokens