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.
npx skills add CharlesWiltgen/Axiom --skill axiom-analyze-triagegit 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/skills/charleswiltgen/axiom/axiom-analyze-triage)<a href="https://agentmods.dev/skills/charleswiltgen/axiom/axiom-analyze-triage"><img src="https://agentmods.dev/badge/skills/charleswiltgen/axiom/axiom-analyze-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/charleswiltgen/axiom/axiom-analyze-triage"><img src="https://agentmods.dev/badge/skills/charleswiltgen/axiom/axiom-analyze-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 36 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00049 | $0.02328 |
| Opus 5 | $0.00024 | $0.01164 |
| Sonnet 5 | $0.00010 | $0.00466 |
| Haiku 4.5 | $0.00005 | $0.00233 |
Grade A, and why
axiom-analyze-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 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: This audit may use Bash commands to run builds, tests, or CLI tools.
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 ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is 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 · 141 lines · 49 tokens per session scan A 9ed28aefdb10
axiom-analyze-triage is a skill published in the GitHub repository CharlesWiltgen/Axiom (1,155 stars, last pushed 3d ago), licensed MIT. It adds 49 tokens to every session and 2,328 once invoked, about $0.0002 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.