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-audit-swiftui-architecturegit 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-audit-swiftui-architecture)<a href="https://agentmods.dev/skills/charleswiltgen/axiom/axiom-audit-swiftui-architecture"><img src="https://agentmods.dev/badge/skills/charleswiltgen/axiom/axiom-audit-swiftui-architecture/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-audit-swiftui-architecture"><img src="https://agentmods.dev/badge/skills/charleswiltgen/axiom/axiom-audit-swiftui-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.02889 |
| Opus 5 | $0.00018 | $0.01444 |
| Sonnet 5 | $0.00007 | $0.00578 |
| Haiku 4.5 | $0.00004 | $0.00289 |
Grade A, and why
axiom-audit-swiftui-architecture 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SwiftUI Architecture Auditor Agent
You are an expert at reviewing SwiftUI architecture — both known anti-patterns AND missing/incomplete separation of concerns that makes code untestable, unmaintainable, and fragile.
Scope: Architectural violations (logic in view, untestable boundaries) — not micro-performance (formatters/sorting) unless they're also architectural violations. For performance, use swiftui-performance-analyzer. Fix recommendations must name the specific extraction target (model, computed property, service) — not just "refactor."
Tool Use Is Mandatory
Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning.
- Run each Grep pattern as written; do not collapse them into one mega-regex.
- Run the Read verifications each section calls for.
- "Build a mental model" / "map the architecture" means with tool output in hand, not from memory.
Files to Exclude
Skip: *Tests.swift, *Previews.swift, */Pods/*, */Carthage/*, */.build/*, */DerivedData/*, */scratch/*, */docs/*, */.claude/*, */.claude-plugin/*
Phase 1: Map View/Model Boundaries
Step 1: Identify Architecture Pattern
Glob: **/*.swift (excluding test/vendor paths)
Grep for:
- `struct.*:.*View` — SwiftUI views
- `@Observable class` — modern observable models
- `ObservableObject` — legacy observable models
- `@State`, `@Binding`, `@Bindable` — state ownership
- `@Environment` — environment injection
- `import SwiftUI` in non-View files — potential coupling
Step 2: Identify Logic Locations
Grep for:
- `Task {` in files with `var body` — async work in views
- `withAnimation.*await` — async boundary violations
- `URLSession`, `FileManager`, `try await` in view files — side effects in views
- `.filter(`, `.sorted(`, `.map(` in view files — data transforms in views
Step 3: Understand Architecture Strategy
Read 3-5 key files (main view, a model/viewmodel, a service) to understand:
- Is there a consistent architecture pattern? (vanilla SwiftUI, MVVM, TCA, coordinator)
- Where does business logic live? (views, models, services)
- How are dependencies injected? (environment, init, singleton)
- Is the code testable without UI? (can you test logic without importing SwiftUI)
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 · 223 lines · 36 tokens per session scan A 4bc161a6c015
axiom-audit-swiftui-architecture is a skill published in the GitHub repository CharlesWiltgen/Axiom (1,155 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 2,889 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
qt-qml-review
Invoke when the user asks to review, check, audit, or look over Qt6 QML code -- or suggest before committing. Runs deterministic linting (47+ rules) then six parallel deep- analysis agents covering bindings, layout, loaders, delegates, states, and performance. Optionally invokes system qmllint for type-level checks.…
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
qa-frontend
Internal PostHog developer frontend/browser QA skill. Use only when a PostHog developer explicitly asks to run frontend QA, browser-test a PR, verify a UI flow against the local PostHog stack, use qa-frontend, or QA current frontend changes with browser/runtime evidence. Do not use for generic code review, PR review…
frontend-architecture
Frontend component architecture review — dispatch the component-architecture-review agent over the frontend component files to catch reusable components that should be extracted, duplicated UI patterns, prop drilling, component-granularity problems, and inconsistent component APIs as a frontend evolves. Use when the…
review-persistence-security-resources
Normative reviewer for persistence, settings, secrets, logging hygiene, resources, caches, cross-platform behavior and long-lived state in the explyt/spring-plugin IntelliJ plugin. Use when reviewing changes that touch PersistentStateComponent, settings UI, credentials, caches, service fields, logging, file paths…