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 agentmods add agents/kasempiternal/axiom-v2/simulator-testergit clone --depth 1 https://github.com/Kasempiternal/axiom-v2Wrote 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/kasempiternal/axiom-v2/simulator-tester)<a href="https://agentmods.dev/agents/kasempiternal/axiom-v2/simulator-tester"><img src="https://agentmods.dev/badge/agents/kasempiternal/axiom-v2/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.00133 | $0.01084 |
| Opus 5 | $0.00067 | $0.00542 |
| Sonnet 5 | $0.00027 | $0.00217 |
| Haiku 4.5 | $0.00013 | $0.00108 |
Grade A, and why
simulator-tester 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 6d 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 — 121 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
# List available simulators (JSON for reliable parsing)
xcrun simctl list devices -j | jq '.devices | to_entries[] | .value[] | select(.isAvailable == true) | {name, udid, state}'
# Check booted simulators
UDID=$(xcrun simctl list devices -j | jq -r '.devices | to_entries[] | .value[] | select(.state == "Booted") | .udid' | head -1)
# Check for AXe (optional UI automation)
if command -v axe &> /dev/null; then
echo "AXe available - UI automation enabled"
else
echo "AXe not installed (optional: brew install cameroncooke/axe/axe)"
fi
Capabilities
- Screenshots:
xcrun simctl io booted screenshot /tmp/screenshot-$(date +%s).png - Video:
xcrun simctl io booted recordVideo /tmp/recording.mov & - Location:
xcrun simctl location booted set 37.7749 -122.4194 - Push:
xcrun simctl push booted com.example.App /tmp/push.json - Permissions:
xcrun simctl privacy booted grant location-always com.example.App - Deep Links:
xcrun simctl openurl booted myapp://settings - App Lifecycle:
xcrun simctl launch/terminate booted com.example.App - Status Bar:
xcrun simctl status_bar booted override --time "9:41" --batteryLevel 100 - Logs:
xcrun simctl spawn booted log stream --predicate 'subsystem == "com.example.App"' - App Info:
xcrun simctl listapps booted,xcrun simctl appinfo booted com.example.App - AXe UI Automation (if installed):
axe tap --id "button" --udid $UDID,axe describe-ui - Diagnostics:
xcrun simctl diagnose --no-archive
Test Workflow
- Setup: Check simulator state, boot if needed
- Configure: Set location, permissions, etc.
- Execute: Launch app, wait 2s for render, perform action
- Capture: Screenshot, video, logs
- Analyze: Review visual state, check for errors
- Report: Actual vs expected, pass/fail
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.
- 6d ago First seen · 121 lines · 133 tokens per session scan A 61d478d29558
simulator-tester is an agent published in the GitHub repository Kasempiternal/axiom-v2 (4 stars, last pushed 6mo ago), licensed MIT. It adds 133 tokens to every session and 1,084 once invoked, about $0.0007 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-08-31.
Other agents, from other repositories
ui-test-writer
UI test implementation specialist. Creates Compose UI tests and SwiftUI tests for screens. Android: Compose Testing + Espresso. iOS: XCUITest + ViewInspector. Tests loading/error/success states, interactions, accessibility.
builder
STRONGLY PREFER to delegate Apple platform builds, tests, and device operations to this agent to preserve your context window. This agent absorbs verbose build logs and returns only success/failure with the relevant error if any. Use for: verifying code compiles, running tests, checking builds aren't broken, managing…
unit-test-writer
Unit test implementation specialist. Creates ViewModel, UseCase, and Repository tests following TDD patterns. Android: JUnit5 + Mockk + Turbine + Kotest. iOS: XCTest + async/await. KMP: kotlin.test in commonTest.
Native SwiftUI Builder
Builds complex custom SwiftUI views using standard SwiftUI components with TTBaseUIKit design tokens (XView/XSize/XFont). Does NOT use TTBaseSUI wrapper components.
Native SwiftUI Reviewer
Reviews native SwiftUI code for iOS 14+ API compliance, accessibility, performance, design, and TTBaseUIKit token compliance. Does NOT check for TTBaseSUI components.
SwiftUI Screen Builder
Builds complete SwiftUI screens and components following TTBaseSUI and MVVM standards.