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/axiom-analyze-crash)<a href="https://agentmods.dev/commands/charleswiltgen/axiom/axiom-analyze-crash"><img src="https://agentmods.dev/badge/commands/charleswiltgen/axiom/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/axiom-analyze-crash"><img src="https://agentmods.dev/badge/commands/charleswiltgen/axiom/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.00022 | $0.00440 |
| Opus 5 | $0.00011 | $0.00220 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
axiom-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 6d 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.
What it actually says
Analyze Crash Log
Use Axiom's structured MCP tools instead of invoking the xcsym helper binary.
- Accept either an existing crash-file path or pasted crash-report content. If neither is present or the input is ambiguous, ask the user for one crash report before continuing.
- For a file path, pass the verified readable file path directly in
file. A readable.xccrashpointbundle path is also valid. Never execute or rewrite a user-supplied path. - For pasted content, create a task-scoped temporary directory with mode
0700and a new file with mode0600outside the repository. Create the file exclusively with a fixed, non-user-derived name and an extension appropriate to JSON or text. Write the content with a filesystem write operation that does not interpolate it into a shell command. Do not include the crash content in a command line, log, diagnostic, or filename. - Call
axiom_xcsym_crashwith the selected path infileand onlysummary,standard, orfullinformat. Usestandardunless the user requests another output tier; pass only other schema-supported fields that the user supplied or the analysis requires. - Interpret the returned pattern, crashed-thread frames, and dSYM completeness even when the tool reports a non-zero completeness status.
- For dSYM mismatches, call
axiom_xcsym_verifywith the same path infile, then callaxiom_xcsym_find_dsymwith the expecteduuidwhen discovery is needed. - After all MCP calls finish or fail, remove only the temporary file and directory created for this request. Never remove or modify a user-supplied crash path.
- Report the likely root cause, evidence, symbolication limits, and concrete next steps.
If a required MCP tool is unavailable, stop and report that the Axiom MCP integration is missing; do not fall back to a same-named executable.
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.
- 6d ago First seen · 19 lines · 22 tokens per session scan A d9137b4add08
axiom-analyze-crash is a command published in the GitHub repository CharlesWiltgen/Axiom (1,155 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 440 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-09-06.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.