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/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/commands/kasempiternal/axiom-v2/test-simulator)<a href="https://agentmods.dev/commands/kasempiternal/axiom-v2/test-simulator"><img src="https://agentmods.dev/badge/commands/kasempiternal/axiom-v2/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/kasempiternal/axiom-v2/test-simulator"><img src="https://agentmods.dev/badge/commands/kasempiternal/axiom-v2/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.00014 | $0.00249 |
| Opus 5.5 | $0.00006 | $0.00100 |
| Sonnet 5.5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
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 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.
What it actually says
Simulator Testing
Launches the simulator-tester agent 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
- UI automation with AXe (if installed)
Prefer Natural Language?
- "Take a screenshot of the app"
- "Test my app with location simulation"
- "Send a test push notification"
- "Navigate to Settings and screenshot"
- "Record a video of the app running"
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 First seen · 39 lines · 14 tokens per session scan A b09a8b28ebba
test-simulator is a command published in the GitHub repository Kasempiternal/axiom-v2 (4 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 249 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-31.
Other commands, from other repositories
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.
feature-verify
Run final verification - pass@k test metrics, coverage report, and sign-off. Confirms feature is production-ready.
ios-test
Bu komut iOS/SwiftUI uygulamasini derleyip simulator'da acarak computer use ile gorsel test yapar.
feature-build-fix
Compile the feature, run all tests, and iteratively fix compilation errors and test failures until everything passes. Max 5 iterations.
mobile-app-testing
Read .cursor/playwright-skills/mobile-app-testing/SKILL.md and follow its instructions exactly. Treat that file's body as your operating instructions for this task. Template files to install live in .cursor/playwright-skills/mobile-app-testing/templates/.