Borrowing it
Nothing to install: this file belongs to r00tify/crashdx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/r00tify/crashdx/main/.claude/skills/crash-triage/SKILL.mdgit clone --depth 1 https://github.com/r00tify/crashdxWrote 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/r00tify/crashdx/crash-triage)<a href="https://agentmods.dev/skills/r00tify/crashdx/crash-triage"><img src="https://agentmods.dev/badge/skills/r00tify/crashdx/crash-triage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/r00tify/crashdx/crash-triage"><img src="https://agentmods.dev/badge/skills/r00tify/crashdx/crash-triage.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00071 | $0.01588 |
| Opus 5 | $0.00036 | $0.00794 |
| Sonnet 5 | $0.00014 | $0.00318 |
| Haiku 4.5 | $0.00007 | $0.00159 |
Grade A, and why
crash-triage 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 10d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apple crash triage with crashdx
The crashdx CLI turns a raw .ips crash report + dSYMs into a symbolicated, diagnosed
report. Trust its JSON over your own reading of the raw file; it encodes ground truth
about .ips quirks that is easy to get wrong (decimal offsets, LEB symbol degradation,
ASI absence patterns).
Invoke it as crashdx if it is on your PATH; otherwise use swift run crashdx … from
the repo root, or .build/debug/crashdx after swift build. The commands below use the
bare name for brevity.
Procedure
-
Analyze first, read raw second:
crashdx analyze <report.ips> --json --tier summarySummary tier is token-lean (faulting thread capped at 15 frames, plus the verdict and ranked hypotheses). Escalate to--tier standard(adds binary images, other threads containing app frames, andfactsConsidered) orfull(every thread, uncapped) only when the verdict is inconclusive or you need cross-thread evidence (deadlocks, lock holders). The diagnosis itself is identical at every tier: it is always computed from the full report, so escalating never changes the verdict, only the evidence you can see. -
dSYMs. If app frames show only offsets (no
symbol), the dSYM wasn't found. Spotlight + Xcode archives are searched automatically;--no-spotlightand--no-archivesturn those off, which is how you keep the user's unrelated projects out of the output. For foreign reports (user emails, CI artifacts), pass the build's dSYM with--dsym <path>(repeatable; accepts a.dSYMbundle, an.xcarchive, or a directory to search recursively).If the
symbolicationkey is absent entirely, crashdx ran no symbolication pass: either every referenced image already carried symbols (the common case for a report analyzed on the machine that produced it), or nothing was found for the images that needed it. Look at the frames to tell which: if app frames havesymbol, nothing was needed. Otherwise checksymbolication.images[].outcome:no_dsym: nothing was found. Go get the dSYM.uuid_mismatch: a dSYM for that image WAS found, but it's from a different build, so it was refused (a stale dSYM yields confidently wrong symbols).reasonnames the offending bundle by absolute path. That path usually sits under the user's~/Library/Developer/Xcode/Archives/and can name their other projects; summarise it, don't paste it anywhere shared. Re-run with--no-spotlight --no-archives --dsym <path>to restrict the search to paths the user named. Don't hunt for a missing file; find the archive matching the report's binary UUID. Never force it through.failed: a dSYM matched but symbolication itself failed;reasonsays why.
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.
- 10d ago First seen · 104 lines · 71 tokens per session scan A 5d9bc4d45cc0
crash-triage is a skill published in the GitHub repository r00tify/crashdx (7 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,588 once invoked, about $0.0004 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
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
native-app-profiling
Profile native macOS/iOS apps using Time Profiler via CLI (xctrace). Use when asked to identify performance hotspots, profile CPU usage, or diagnose slow code paths without opening Instruments.
performance-audit
Audit and improve SwiftUI runtime performance. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps.
Debroid CLI Debugger
Orchestrate headless Android debugging via JDWP. ACTIVATE this skill whenever asked to debug an Android application, set line or exception breakpoints, inspect runtime variables or Jetpack Compose state, step through execution, evaluate live expressions, watch fields, or diagnose runtime crashes.
symbolication-setup
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
network-tracing
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.