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.
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.
git clone --depth 1 https://github.com/CharlesWiltgen/AxiomWrote 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/commands/charleswiltgen/axiom/analyze-crash)<a href="https://agentmods.dev/commands/charleswiltgen/axiom/analyze-crash"><img src="https://agentmods.dev/badge/commands/charleswiltgen/axiom/analyze-crash/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/commands/charleswiltgen/axiom/analyze-crash"><img src="https://agentmods.dev/badge/commands/charleswiltgen/axiom/analyze-crash.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.00029 | $0.00307 |
| Opus 5 | $0.00015 | $0.00153 |
| Sonnet 5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
analyze-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- analyze-crash — 92% identical, 9 lines differ
What it actually says
Analyze Crash Log
Launches the crash-analyzer agent to parse crash reports and identify the root cause.
What It Does
The agent will:
- Parse the crash report (JSON .ips or text .crash format)
- Extract key fields (exception type, codes, crashed thread, frames)
- Check symbolication status
- Categorize by crash pattern (null pointer, Swift runtime, watchdog, jetsam, etc.)
- Generate actionable analysis with specific next steps
Crash Sources
Provide crashes via:
- Pasted text — Copy/paste the crash report directly
- File path —
~/Library/Logs/DiagnosticReports/MyApp.ips - Xcode export — Copied from Organizer
Crash Log Locations
# macOS/iOS Simulator crash logs
~/Library/Logs/DiagnosticReports/*.ips
# Device crash logs (after sync)
~/Library/Logs/CrashReporter/MobileDevice/<DeviceName>/
Prefer Natural Language?
You can also trigger this agent by saying:
- "Analyze this crash log"
- "Here's a crash from TestFlight, what's wrong?"
- "Parse this .ips file"
- "Why did my app crash? Here's the report..."
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 · 44 lines · 29 tokens per session scan A bd2f932107d8
analyze-crash is a command published in the GitHub repository CharlesWiltgen/Axiom (1,151 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 307 once invoked, about $0.0001 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.
Other commands, from other repositories
flutter-build
Fix Dart analyzer errors and Flutter build failures incrementally. Invokes the dart-build-resolver agent for minimal, surgical fixes.
decompile
Decompile an Android APK/XAPK/JAR/AAR and analyze its structure.
safe-decompile
Safely fingerprint and decompile an Android artifact through the sandboxed MCP server.
proguard
Command "proguard" from getsentry/cli, covering examples, compute the uuid for a proguard/r8 mapping file, output as json (includes the file path) and important notes.
debug
Debug Purchasely SDK issues — diagnose blank paywalls, frozen UI, purchase failures, and more.
xcode-build-fix
Incrementally fix Xcode build and Swift compiler errors. Parse errors, explain issues, apply fixes, verify resolution.