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/axiom-test-simulator)<a href="https://agentmods.dev/commands/charleswiltgen/axiom/axiom-test-simulator"><img src="https://agentmods.dev/badge/commands/charleswiltgen/axiom/axiom-test-simulator/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/axiom-test-simulator"><img src="https://agentmods.dev/badge/commands/charleswiltgen/axiom/axiom-test-simulator.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.00020 | $0.00406 |
| Opus 5 | $0.00010 | $0.00203 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
axiom-test-simulator 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.
This is a copy
94% identical to test-simulator — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Simulator Testing Agent
Delegate to the simulator-tester subagent for automated simulator testing with visual verification.
What It Does
The agent will:
- Check simulator state and boot if needed
- Set up test scenarios (location, permissions, push notifications)
- Capture screenshots and video
- Monitor logs for crashes/errors
- Analyze results and provide clear reports
Capabilities
- Screenshot capture for visual debugging
- Video recording for complex workflows
- Location simulation for GPS-based features
- Push notification testing without a server
- Permission management without manual tapping
- Deep link navigation to specific screens
- Status bar override for clean screenshots
- Log analysis for crash detection
Common Scenarios
Visual Verification:
/axiom-test-simulator
"Take a screenshot to verify the login button fix"
Location Testing:
/axiom-test-simulator
"Set location to San Francisco and test the map feature"
Push Notifications:
/axiom-test-simulator
"Send a test push notification and screenshot the result"
Permission Flows:
/axiom-test-simulator
"Test the camera permission dialog"
Prefer Natural Language?
Instead of using this command, you can simply say:
- "Can you take a screenshot of the app?"
- "Test my app with location simulation"
- "Check if the push notification handling works"
- "Navigate to Settings and take a screenshot"
- "Record a video of the app running"
The simulator-tester agent will automatically trigger.
Quick Screenshot
For just a quick screenshot without full testing, use:
/axiom-screenshot
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 · 74 lines · 20 tokens per session scan A 1c148f92b12d
axiom-test-simulator is a command published in the GitHub repository CharlesWiltgen/Axiom (1,151 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 406 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to test-simulator, differing in 18 lines, and is treated as a copy.
Other commands, from other repositories
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
feature-test
Create all tests for an implemented feature - unit tests (ViewModel, UseCase, Repository), Compose UI tests, and E2E user flow tests.
xcuitest
Generate and run end-to-end tests with XCUITest. Creates test journeys using Page Object Model, runs tests, captures screenshots/videos, and manages flaky tests.