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/compare-traces)<a href="https://agentmods.dev/commands/charleswiltgen/axiom/compare-traces"><img src="https://agentmods.dev/badge/commands/charleswiltgen/axiom/compare-traces/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/compare-traces"><img src="https://agentmods.dev/badge/commands/charleswiltgen/axiom/compare-traces.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.00015 | $0.00730 |
| Opus 5 | $0.00008 | $0.00365 |
| Sonnet 5 | $0.00003 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
compare-traces 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compare Performance Traces
Diffs two Instruments .trace recordings with xcprof compare — function-level CPU-share deltas, regressions separated from improvements, and a non-zero exit code your CI can gate on. Replaces the old "export both traces and eyeball the XML" workflow.
When to Use
- Verify a change didn't slow down a hot path ("did this PR regress CPU?").
- Gate a merge on performance (fail when a function's CPU share jumps past a threshold).
- Quantify an optimization (the improvement list shows what got faster).
Steps
-
Verify the tool.
command -v xcprof && xcprof doctor. Ifxcprofis missing, the Axiom install is stale — tell the user to update Axiom. -
Get two traces. Either the user already has
baseline.trace+current.trace, or capture them. Both recordings MUST exercise the same workload (same UI flow / benchmark), or the deltas measure workload differences, not regressions:export XCPROF_TRACE_ROOT="$(mktemp -d)" # before-revision build, exercise the hot path: xcprof record --preset cpu --attach MyApp --time-limit 15s --no-prompt \ --output "$XCPROF_TRACE_ROOT/baseline.trace" # after-revision build, exercise the SAME path: xcprof record --preset cpu --attach MyApp --time-limit 15s --no-prompt \ --output "$XCPROF_TRACE_ROOT/current.trace" -
Compare. Default output is compact JSON; add
--humanto read it:xcprof compare baseline.trace current.trace --humanFor a CI gate, add
--fail-on-regression(exit 3 when any function's inclusive CPU share rose ≥--threshold-pct, default 5):xcprof compare baseline.trace current.trace --fail-on-regression --threshold-pct 5 -
Interpret honestly. Report the regressions (sorted by severity = % delta × absolute time) and improvements. Note when frames were excluded for being unsymbolicated (pass
--dsymfor release builds). Deltas are percentage-points of CPU-cycle share — the only quantity comparable across two runs of different total work.
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 · 61 lines · 15 tokens per session scan A 1def14c87ad7
compare-traces is a command published in the GitHub repository CharlesWiltgen/Axiom (1,151 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 730 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
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.