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/Kasempiternal/axiom-v2Wrote 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/kasempiternal/axiom-v2/analyze-crash)<a href="https://agentmods.dev/commands/kasempiternal/axiom-v2/analyze-crash"><img src="https://agentmods.dev/badge/commands/kasempiternal/axiom-v2/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/kasempiternal/axiom-v2/analyze-crash"><img src="https://agentmods.dev/badge/commands/kasempiternal/axiom-v2/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.00294 |
| Opus 5 | $0.00015 | $0.00147 |
| Sonnet 5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00029 |
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 9d 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.
This is a copy
92% identical to analyze-crash — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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?
- "Analyze this crash log"
- "Here's a crash from TestFlight, what's wrong?"
- "Parse this .ips file"
- "Why did my app crash?"
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.
- 9d ago First seen · 43 lines · 29 tokens per session scan A db7b1a8edbbe
analyze-crash is a command published in the GitHub repository Kasempiternal/axiom-v2 (4 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 294 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to analyze-crash, differing in 9 lines, and is treated as a copy.
Other commands, from other repositories
feature-learn
View and manage patterns learned from feature builds. Shows extracted instincts, confidence scores, and feature completeness history.
feature-status
Show the current status of a feature build - which phase is active, what has completed, what remains, and any blockers.
add-accessibility
SwiftUI view'lara accessibility identifier ekle. "accessibility ekle", "identifier ekle", "test icin etiketle", "VoiceOver destegi ekle", "erisilebilirlik ekle" gibi isteklerde tetiklenir.
ml-impl
Full implementation loop - plan, write, and review code (Meta-Loop Steps 3.1-3.4).
ml-spec
Full specification loop - plan, write, and review spec (Meta-Loop Steps 2.1-2.4).
checklist
Generate a custom checklist for the current feature based on user requirements.