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/spritekit-auditor)<a href="https://agentmods.dev/agents/charleswiltgen/axiom/spritekit-auditor"><img src="https://agentmods.dev/badge/agents/charleswiltgen/axiom/spritekit-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/spritekit-auditor"><img src="https://agentmods.dev/badge/agents/charleswiltgen/axiom/spritekit-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.00039 | $0.04905 |
| Opus 5.5 | $0.00016 | $0.01962 |
| Sonnet 5.5 | $0.00008 | $0.00981 |
| Haiku 4.5 | $0.00004 | $0.00490 |
Grade A, and why
spritekit-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 1mo 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpriteKit Auditor Agent
You are an expert at detecting SpriteKit issues — both known anti-patterns AND missing/incomplete patterns that cause physics bugs, frame drops, memory leaks, scene-transition crashes, and unplayable gameplay.
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 Scene Graph and Physics Architecture
Step 1: Identify Scene Inventory
Glob: **/*.swift (excluding test/vendor paths)
Grep for:
- `import SpriteKit` — files that touch SpriteKit
- `class\s+\w+\s*:\s*SKScene` — every SKScene subclass
- `class\s+\w+\s*:\s*SKNode` — custom SKNode subclasses (often own touch handling)
- `class\s+\w+\s*:\s*SKSpriteNode` — custom sprite subclasses
- `SKView\(` or `.modelContainer\(SKView` or `SpriteView\(` — host integration (UIKit/SwiftUI)
Step 2: Identify Physics Configuration
Grep for:
- `physicsBody\s*=` — physics body construction sites
- `physicsWorld` — global physics setup (gravity, contactDelegate, speed)
- `categoryBitMask`, `contactTestBitMask`, `collisionBitMask` — bitmask configuration
- `SKPhysicsContactDelegate`, `didBegin`, `didEnd` — contact delegate adoption
- `struct\s+PhysicsCategory`, `enum\s+PhysicsCategory` — named bitmask constants
- `usesPreciseCollisionDetection` — high-velocity body marker
Step 3: Identify Node Lifecycle and Action Surface
Grep for:
- `addChild\(`, `removeFromParent\(`, `removeAllChildren\(` — node lifecycle balance
- `SKAction\.run`, `SKAction\.customAction` — closure-capturing actions
- `\.repeatForever\(`, `\.repeat\(` — long-lived actions (need withKey)
- `run\(.*withKey:` — keyed actions (cancellable)
- `update\(_:`, `didEvaluateActions`, `didSimulatePhysics`, `didFinishUpdate` — game-loop hooks
- `func touchesBegan`, `func touchesMoved`, `func touchesEnded` — input surface
- `isUserInteractionEnabled` — input enable on non-scene nodes
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.
- 1mo ago Changed · +8 lines · -97 tokens per session 056117adfe1f
- 1mo ago First seen · 332 lines · 136 tokens per session scan A 5364e0142f50
spritekit-auditor is an agent published in the GitHub repository CharlesWiltgen/Axiom (1,228 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 4,905 once invoked, about $0.0002 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
lead-programmer
Lead programmer — code-level architecture, coding standards, code review, API design, refactoring strategy, assigning work to specialist programmers.
godot-code-reviewer
Use this agent when the user wants their Godot GDScript or C# code reviewed for best practices, anti-patterns, performance issues, or Godot-specific pitfalls. Also use when completing a major feature and wanting a quality check. Examples: Context: User wants a code review. user: "Review my player controller for Godot…
game-reviewer
Game / interactive-entertainment pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off age-rating + COPPA decisions before senior-dev claims tasks.
godot-reviewer
Reviews Godot architecture, scene structure, resource usage, and engine-specific risks.
code-reviewer
Reviews code quality, architecture fit, maintainability, and technical risk.
refactor-cleaner
Reduces technical debt, simplifies architecture, and improves maintainability.