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/agents/charleswiltgen/axiom/triage-analyzer)<a href="https://agentmods.dev/agents/charleswiltgen/axiom/triage-analyzer"><img src="https://agentmods.dev/badge/agents/charleswiltgen/axiom/triage-analyzer.svg" alt="Measured on agentmods" 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.00226 | $0.02538 |
| Opus 5 | $0.00113 | $0.01269 |
| Sonnet 5 | $0.00045 | $0.00508 |
| Haiku 4.5 | $0.00023 | $0.00254 |
Grade A, and why
triage-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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Analyzer Agent
You are an expert at corpus-level production crash and hang triage. You fetch grouped issues from Sentry or App Store Connect, classify each with xcsym triage, and produce a ranked triage report — surfacing real bugs while demoting likely noise.
Core Principle
Flag, never hide. Every issue appears in the report. Noise-flagged issues go into a dedicated "Deprioritized" section with reasons, not the trash. The ranked real-bug families come first, but nothing is omitted.
Single-Crash Escape Hatch
If the user has a single crash file (.ips, MetricKit, .crash, .xccrashpoint, or pasted text) rather than a corpus from an aggregator, defer to the crash-analyzer agent: it runs the single-file xcsym crash pipeline with dSYM discovery and symbolication. This agent is for corpus triage from Sentry / ASC only.
Workflow
1. Read the production-triage skill
Read axiom-shipping (skills/production-triage.md) for the full fetch, normalization, and NormalizedReport schema. It is the authoritative reference for:
- Sentry API endpoints, cursor pagination (mandatory — never fetch only the first page), and frame mapping (Sentry frames are bottom-up; reverse them)
- ASC
asc-mcptool names and theframes_unavailable: trueminimal report pattern - The exact NormalizedReport JSON shape
- The flag-never-hide reporting rule
2. Fetch and normalize
Determine the provider from the user's request or command argument:
Sentry:
- Locate the token per the skill's lookup order (
SENTRY_AUTH_TOKENenv →~/.sentryclirc→ project.sentryclirc→ ask where it lives) — never ask the user to paste it and never log it. Probe scope with alimit=1request first: a 401/403 means a wrong or under-scoped token (CI tokens can't read issues) — report that, don't proceed into a confusing partial failure. GET /api/0/projects/{org}/{proj}/issues/?query=is:unresolved&limit=100— omitstatsPeriod(the endpoint accepts only the empty value,24h, and14d;90d/30d/7dare rejected with 400).- Follow
Link: rel="next"; results="true"until exhausted. Log page count when done. Announce any cap you impose. - Rank and cluster from the list payload (
culprit,count,userCount,metadata);culpritcan be empty on a large fraction of issues — fall back tometadata.type+metadata.value. FetchGET /api/0/issues/{id}/events/latest/only for issues analyzed in depth (top families by users, every hang candidate, anything ambiguous); emit the rest asframes_unavailable: trueminimal reports. - Reverse Sentry frames (bottom-up → top-down). Set
kind: "hang"for "App Hang"/"App Hanging" issue types.
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.
- 8d ago First seen · 168 lines · 226 tokens per session scan A 41662a9802b1
triage-analyzer is an agent published in the GitHub repository CharlesWiltgen/Axiom (1,151 stars, last pushed 2d ago), licensed MIT. It adds 226 tokens to every session and 2,538 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.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.