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-codablegit 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-codable)<a href="https://agentmods.dev/skills/charleswiltgen/axiom/axiom-audit-codable"><img src="https://agentmods.dev/badge/skills/charleswiltgen/axiom/axiom-audit-codable/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-codable"><img src="https://agentmods.dev/badge/skills/charleswiltgen/axiom/axiom-audit-codable.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 Rogue Agent · line 42 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00032 | $0.04484 |
| Opus 5 | $0.00016 | $0.02242 |
| Sonnet 5 | $0.00006 | $0.00897 |
| Haiku 4.5 | $0.00003 | $0.00448 |
Grade A, and why
axiom-audit-codable 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 4d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codable Auditor Agent
You are an expert at detecting Codable safety violations — both known anti-patterns AND missing/incomplete patterns that cause silent data loss, revenue leaks, and production crashes.
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 Serialization Architecture
Step 1: Inventory Codable Types
Glob: **/*.swift (excluding test/vendor paths)
Grep for:
- `: Codable`, `: Decodable`, `: Encodable` — Conformances
- `init(from decoder:` — Manual decode implementations
- `encode(to encoder:` — Manual encode implementations
- `@propertyWrapper` on Codable-conforming types — Custom wrappers
- `DecodableWithConfiguration` — iOS 15+ injected-data decoding
- `CodingKeys` — Explicit key mapping
Step 2: Inventory Encoder/Decoder Sites
Grep for:
- `JSONDecoder()`, `JSONEncoder()` — Instantiation points
- `PropertyListDecoder()`, `PropertyListEncoder()` — Plist variants
- `dateDecodingStrategy`, `dateEncodingStrategy` — Date configuration
- `keyDecodingStrategy`, `keyEncodingStrategy` — Key configuration
- `JSONSerialization` — Legacy serialization
- `.jsonObject(with:`, `.data(withJSONObject:` — JSONSerialization call sites
Step 3: Map Serialization Boundaries
Read 2-3 key files (one API model, one decoder usage site, any custom codable wrapper) to understand:
- What Codable types cross which boundaries (network, disk, inter-process, pasteboard)
- Which decoders/encoders are shared across files and which are one-offs
- Whether date and key strategies are consistent per-boundary or drift between sites
- Whether any types are encoded in one file and decoded in another (round-trip)
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.
- 4d ago First seen · 274 lines · 32 tokens per session scan A ac5d8c946dca
axiom-audit-codable is a skill published in the GitHub repository CharlesWiltgen/Axiom (1,151 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 4,484 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
kotlin-concurrency-and-flow
Use when writing or reviewing Kotlin coroutine scope ownership, raw Thread or Executor work, init launches, non-suspending launch APIs, runBlocking, cancellation, StateFlow, SharedFlow, Channel, stateIn, SharingStarted, state updates, or one-shot events.
kotlin-api-design
Use when designing or reviewing Kotlin function ownership, member or extension functions, factories, single-field domain types, value classes, data classes, Kotlin Multiplatform expect/actual declarations, or platform service boundaries.
coding-best-practices
Reviews Swift/iOS code for adherence to modern Swift idioms, Apple platform best practices, architecture patterns, and code quality standards. Use when user mentions best practices, code review, clean code, refactoring, or wants to improve code quality.
adversarial-swift
Use this skill to gate Swift language code with a pass/fail adversarial review — a single blind reviewer subagent judges a diff or file set against 36 decidable rules covering concurrency (unresumed continuations, cancellation checks, async let, TaskGroup, @concurrent), property invariants (stored-derived state…
swift-concurrency-review
Review Swift 6 strict-concurrency and SwiftUI code for idiom and build-breaking issues - non-Sendable across actor boundaries, @MainActor witness vs nonisolated protocol requirements, Combine/ObservableObject usage, force-unwraps, #Predicate macro limits, the 6.3.x Binding IRGen crash, missing #if os() guards, and…
writing-java-kotlin
Idiomatic modern Java and Kotlin JVM development. Use when writing .java, .kt, or .kts code; changing Gradle or Maven builds; or working on Spring, Micronaut, Quarkus, Ktor, Android JVM modules, JUnit, Mockito, Kotest, ktlint, detekt, or JVM CLI/services. Emphasizes JDK toolchains, null-safety, fast focused…