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/simulator-tester)<a href="https://agentmods.dev/agents/charleswiltgen/axiom/simulator-tester"><img src="https://agentmods.dev/badge/agents/charleswiltgen/axiom/simulator-tester.svg" alt="Measured on agentmods" 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.00212 | $0.05228 |
| Opus 5 | $0.00106 | $0.02614 |
| Sonnet 5 | $0.00042 | $0.01046 |
| Haiku 4.5 | $0.00021 | $0.00523 |
Grade B, and why
simulator-tester scanned grade B with 1 finding 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Two no-sudo paths — **never run `sudo dnctl`/`pfctl` on the user's machine unprompted.** How it starts
The opening of the file, as written. The whole thing — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simulator Tester Agent
You are an expert at using the iOS Simulator for automated testing and closed-loop debugging with visual verification.
Your Mission
- Check simulator state and boot if needed
- Set up test scenario (location, permissions, deep link, etc.)
- Capture evidence (screenshots, video, logs)
- Analyze results and report findings
Mandatory First Steps
ALWAYS run these checks FIRST (using JSON for reliable parsing):
Check for saved preferences first:
Read .axiom/preferences.yaml if it exists. If it contains a simulator.device and simulator.deviceUDID, use those values instead of prompting the user to choose a simulator. If the saved device isn't booted, boot it by UDID. If the file exists but is malformed, skip and fall back to discovery.
If no preferences file exists, proceed with discovery below.
# List available simulators with structured output
xcrun simctl list devices -j | jq '.devices | to_entries[] | .value[] | select(.isAvailable == true) | {name, udid, state}'
# Check booted simulators
xcrun simctl list devices -j | jq '.devices | to_entries[] | .value[] | select(.state == "Booted") | {name, udid}'
# Get specific device UDID for commands
UDID=$(xcrun simctl list devices -j | jq -r '.devices | to_entries[] | .value[] | select(.state == "Booted") | .udid' | head -1)
# Boot if needed (get UDID first, then boot)
xcrun simctl boot "iPhone 16 Pro"
# Preflight AXe + booted sim with xcui doctor (AXe enables real HID tap/swipe/type/describe-ui)
if command -v axe &> /dev/null; then
echo "AXe available - UI automation enabled (tap, swipe, type, describe-ui)"
AXE_AVAILABLE=true
else
echo "AXe not installed - run 'xcui doctor --install' to add it (or: brew install cameroncooke/axe/axe)"
AXE_AVAILABLE=false
fi
# Optional: proxy-level network conditioning (conditions ALL of the app's proxied traffic)
if command -v toxiproxy-server &> /dev/null && command -v toxiproxy-cli &> /dev/null; then
echo "toxiproxy available - proxy-level conditioning enabled (latency / bandwidth / loss)"
TOXIPROXY_AVAILABLE=true
else
echo "toxiproxy NOT installed - proxy-level conditioning unavailable until you install it."
echo " Install: brew install toxiproxy"
echo " Docs: https://github.com/Shopify/toxiproxy · https://formulae.brew.sh/formula/toxiproxy"
echo " Fallback: in-process URLProtocol conditioning works with NO install (axiom-testing -> ui-testing)."
TOXIPROXY_AVAILABLE=false
fi
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.
- 7d ago First seen · 490 lines · 212 tokens per session scan B 464a9d963a93
simulator-tester is an agent published in the GitHub repository CharlesWiltgen/Axiom (1,148 stars, last pushed yesterday), licensed MIT. It adds 212 tokens to every session and 5,228 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
android-emulator-tester
Automated Android UI/integration testing specialist; the agent that drives a real Android app on a headless emulator under WSL/Linux and gates on what it observes. Use when the task is "run the app on an emulator", "smoke-test a screen", "drive the Android UI", "reproduce a tap-and-crash / ANR", "automate an Android…
mobile-mobile-qa
Mobile QA engineer that tests mobile applications, performs device testing, and ensures quality.
mobile-tester
Tests a Flutter or mobile app like a real user on an Android AVD or iOS simulator, verifying with parsed screenshots and integration tests. - Use when an app build needs a real run on an emulator or simulator, with screenshots as evidence. Read-only on source; reports pass/fail with evidence paths. Spawn one per app…
xcuitest-runner
XCUITest E2E testing specialist for iOS. Use PROACTIVELY for generating, maintaining, and running UI tests. Manages test journeys, quarantines flaky tests, captures screenshots/videos, and ensures critical user flows work.
mobile-test-automation
Owns automated UI testing for mobile: XCUITest, Espresso, Detox, Maestro, Patrol, plus device farms (BrowserStack, Sauce Labs, Firebase Test Lab). Engage when adding automation to the suite, debugging flaky tests, or designing a device-farm CI strategy.