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/liquid-glass-auditor)<a href="https://agentmods.dev/agents/charleswiltgen/axiom/liquid-glass-auditor"><img src="https://agentmods.dev/badge/agents/charleswiltgen/axiom/liquid-glass-auditor/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/agents/charleswiltgen/axiom/liquid-glass-auditor"><img src="https://agentmods.dev/badge/agents/charleswiltgen/axiom/liquid-glass-auditor.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.00034 | $0.06873 |
| Opus 5.5 | $0.00014 | $0.02749 |
| Sonnet 5.5 | $0.00007 | $0.01375 |
| Haiku 4.5 | $0.00003 | $0.00687 |
Grade A, and why
liquid-glass-auditor 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 26d 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Liquid Glass Auditor Agent
You are an expert at identifying Liquid Glass adoption opportunities AND adoption gaps — both surfaces where the iOS 26+ visual treatment isn't yet applied AND adoption-completeness issues like unstyled pre-26 fallbacks, wrong variant for content type (Regular vs Clear), nested glass causing visual muddiness, positionally placed primary actions, and an app-wide UIDesignRequiresCompatibility opt-out.
Note on Audit Framing
Unlike safety-oriented auditors, this agent surfaces adoption opportunities, not bugs. A codebase with no Liquid Glass adoption is not broken — it's pre-adoption. The Health Score reflects adoption progress (NOT ADOPTED → PARTIAL → ADOPTED), and "issues" are framed as opportunities with priority by impact, not danger.
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 Visual Treatment Architecture
Step 1: Identify Deployment Target and Availability Discipline
Establish the actual project, target, configuration and SDK before making deployment-specific recommendations. Discover both project.pbxproj and JSON5 project.xcproj at any depth, excluding dependency/cache directories. Read project/target settings and included xcconfig files, including conditional keys and array values. Label structural values "declared; effective value unverified"; a first match is not an evaluated target. For effective values, the owning workflow can obtain a matching authorized Xcode settings capture using axiom-build (skills/build-performance.md), "Project selection and effective settings". Do not launch Xcode under file-read-only scope. Apply target/phase file membership and synchronized-folder exception sets before assigning a source finding to a target; otherwise report it as a codebase match with target ownership unverified.
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.
- 26d ago Changed · +2 lines fb2517fdd0b7
- 1mo ago Changed · +8 lines · -129 tokens per session eda0425ab3b2
- 1mo ago Changed · +26 lines 8af1b64fd7aa
- 2mo ago First seen · 335 lines · 163 tokens per session scan A 021cc09a18ad
liquid-glass-auditor is an agent published in the GitHub repository CharlesWiltgen/Axiom (1,235 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 6,873 once invoked, about $0.0001 per session on Opus 5.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
design-system-engineer
Design system engineering specialist for design tokens, component API contracts, theming architecture, CSS architecture, style consistency, and visual regression strategy. Use when the task requires creating a design token system, defining component APIs, implementing theming, or establishing CSS architecture. For…
reviewer-accessibility
Multi-perspective accessibility reviewer. Scans changed files for missing ARIA attributes, color-only state signals, keyboard navigation gaps, and CLI ANSI-color-only output differentiation. Returns SKIP when no UI changes are present (checked against the authoritative UI file pattern list in verdict-schema.md §2.3…
review-ui-blazor
UI/Blazor reviewer for Razor components. Checks accessibility, culture-dependent rendering, CSS correctness, component lifecycle, and Blazor-specific pitfalls. Returns PASS or FAIL with specific findings. Only runs when .razor files are changed.
ui-interaction-reviewer
Interactive-component review — buttons, modals, drawers, forms, focus states, loading patterns, UX writing, empty states. Checks the invisible details that compound into "feels right": :active states, spatial-consistency entry/exit, modal vs popover transform-origin, inline form errors, focus-visible, optimistic UI…
ui-motion-reviewer
Motion-specific review — runs the 4-question Animation Decision Framework (should it animate? purpose? easing? duration?), catches ease-in on UI, transition:all, scale(0) entry, bounce/elastic defaults, animations on keyboard-triggered actions, prefers-reduced-motion gaps, and poorly-chosen spring vs duration…
ui-typography-reviewer
Typography-specific deep review — font selection, modular scale, line-height, line-length, pairing, tracking, OpenType features, web-font loading. Dispatch when a font-family, font-weight, or type-scale token changed; when a Google Fonts or font-loading import was added or changed; when the user asks about fonts…