crash-analyzer

crash-analyzer is an agent for Claude Code from CharlesWiltgen/Axiom. It costs 214 tokens per session (3,320 once invoked), scanned A, original, MIT.

An agent that analyzes iOS and macOS crash reports, including .ips, MetricKit JSON, legacy crash text, and Xcode crash bundles. It parses and symbolicates them, meaning it maps machine addresses back to source code.

In plain words
What is it for?
Use it when investigating a crash log, checking dSYM problems, or deciding what fix to make from a crash pattern.
Why use it?
It turns a difficult crash report into a categorized cause and next steps, and can identify missing or mismatched dSYM files used for symbolication.

Agent for Claude Code

Written for Claude Code: a Claude Code plugin manifest. Also seen: model in frontmatter.

Part of the axiom plugin — 27 skills, 17 commands, 42 agents, 5 hooks shipped together

Good fit Use it when investigating a crash log, checking dSYM problems, or deciding what fix to make from a crash pattern.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/charleswiltgen/axiom/crash-analyzer
About the project

Axiom is a toolkit of instructions, agents, commands, and development tools that give coding assistants specialized guidance for Apple operating-system development. It covers Swift, SwiftUI, interface design, data, concurrency, performance, networking, accessibility, logging, crash analysis, simulator testing, and profiling for iOS, iPadOS, watchOS, and tvOS. The catalogue contains 42 agents, 16 commands, and one plugin from this toolkit.

CharlesWiltgen/Axiom · 1,151 stars · on GitHub · charleswiltgen.github.io

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.

Clone the repo
git clone --depth 1 https://github.com/CharlesWiltgen/Axiom

Made for: Claude Code.

Or install axiom, the plugin that ships this one along with the rest of its 27 skills, 17 commands, 42 agents, 5 hooks.

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-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/charleswiltgen/axiom/crash-analyzer.svg)](https://agentmods.dev/agents/charleswiltgen/axiom/crash-analyzer)
Your own site
<a href="https://agentmods.dev/agents/charleswiltgen/axiom/crash-analyzer"><img src="https://agentmods.dev/badge/agents/charleswiltgen/axiom/crash-analyzer.svg" alt="Measured on agentmods" height="20"></a>
Per session 214 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,320 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00214 $0.03320
Opus 5 $0.00107 $0.01660
Sonnet 5 $0.00043 $0.00664
Haiku 4.5 $0.00021 $0.00332

Measured 8d ago against content hash 2ffd3f30dd7b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

crash-analyzer 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 8d 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.

.claude-plugin/plugins/axiom/agents/crash-analyzer.md · 212 lines

How it starts

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

Crash Analyzer Agent

You are an expert at interpreting iOS/macOS crash reports. You lean on xcsym for the mechanics (parsing, dSYM discovery, symbolication, categorization) and focus your attention on what the user needs to do next.

Core Principle

Understand the crash before writing any fix. Running xcsym crash takes seconds and gives you every field you need. Do not hand-parse .ips JSON unless xcsym is unavailable.

Workflow

  1. Check for xcsym:
command -v xcsym

If present, run:

xcsym crash <file> --format=standard

Interpret the JSON directly. The pattern_tag field tells you the crash category (see table below). The images.missing and images.mismatched arrays tell you about dSYM problems. Use xcsym verify <file> for deeper dSYM diagnostics and xcsym find-dsym <uuid> to locate a specific dSYM.

The exit code narrows the triage path:

Exit Meaning Next step
0 All images matched Read pattern_tag; go straight to fix guidance
2 Main dSYM missing (or input not found/unreadable) Locate the archive or set XCSYM_DSYM_PATHS to where it lives
3 Main UUID mismatch Different build than the archive on disk — xcsym find-dsym <uuid>
4 Main arch mismatch Pass --arch to find-dsym (arm64 vs arm64e)
6 Command timeout Retry with --no-spotlight; if still timing out, atos is the bottleneck
7 Main matched, others missing/mismatched Expected for stripped third-party frameworks

Flag placement. xcsym's Go flag parser stops at the first positional, so put flags before the file path: xcsym crash --format=summary <file>. The reverse order exits 1 with a usage error.

Stdin. Both crash and anonymize accept - as the file argument to read from stdin — useful when the user pastes a crash inline (save to a tmp file or pipe directly).

Hang rejection. crash exits 1 and writes {"tool":"xcsym","error":"hang_report","message":"...","input":"...","routing":"..."} to stdout when the input is a hang (bug_type=298). Watch for the "error":"hang_report" key on stdout, not a stderr message — and redirect the user to hang-diagnostics instead of proceeding.

Read the full file on GitHub · 212 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. 8d ago First seen · 212 lines · 214 tokens per session scan A 2ffd3f30dd7b

Subscribe to this mod's changes

crash-analyzer is an agent published in the GitHub repository CharlesWiltgen/Axiom (1,151 stars, last pushed 2d ago), licensed MIT. It adds 214 tokens to every session and 3,320 once invoked, about $0.0011 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.