axe-ios-simulator
Automate iOS Simulator Testing with AXe
iOS simulator testing often needs repeatable taps, text entry, screenshots, and accessibility checks. This skill provides AXe CLI command patterns for Claude, Codex, and Claude Code workflows.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "axe-ios-simulator" from https://skillstore.io/skills/0xbigboss-axe-ios-simulator.md and its manifest at https://skillstore.io/api/skills/0xbigboss-axe-ios-simulator/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "axe-ios-simulator". Capture the state after I submit the test form.
Expected outcome:
The result includes the selected simulator, the action sequence, a final screenshot path, and notes about visible success or error states.
Using "axe-ios-simulator". Check whether the current screen exposes useful accessibility labels.
Expected outcome:
The result summarizes the visible accessibility tree, highlights missing labels, and names stable identifiers for future automation.
Using "axe-ios-simulator". Record a short simulator video for a bug report.
Expected outcome:
The result describes the recording settings, the saved video location, and any sensitive UI areas to review before sharing.
Security Audit
Medium RiskMost static findings are Markdown command examples or inline backticks, not hidden code execution. Real residual risks are the third-party AXe installation and expected simulator capture or UI inspection commands, which can expose sensitive test data.
Confirmed security concerns (12)
Show all 12 confirmed findings
Risk Factors
⚙️ External commands (32)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/0xbigboss-axe-ios-simulator/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/0xbigboss-axe-ios-simulator?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/0xbigboss-axe-ios-simulator?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/0xbigboss-axe-ios-simulator/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/0xbigboss-axe-ios-simulator.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
0xBigBoss. (2026). axe-ios-simulator security audit report (audit version 11) [Author version unspecified]. Skillstore. https://skillstore.io/skills/0xbigboss-axe-ios-simulator/audits/11BibTeX citation
@techreport{0xbigboss-0xbigboss-axe-ios-simulator-2026,
author = {0xBigBoss},
title = {axe-ios-simulator security audit report (audit version 11)},
institution = {Skillstore},
year = {2026},
number = {11},
url = {https://skillstore.io/skills/0xbigboss-axe-ios-simulator/audits/11},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "axe-ios-simulator security audit report (audit version 11)"
version: "unspecified"
type: report
authors:
- name: "0xBigBoss"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/0xbigboss-axe-ios-simulator/audits/11"
identifiers:
- type: other
value: "skillstore:0xbigboss-axe-ios-simulator:audit:11"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Repeat Simulator Smoke Tests
Run predictable taps, swipes, text entry, and screenshots during manual release checks.
Capture App States Quickly
Record simulator video or screenshots after key UI actions for bug reports and design review.
Inspect Accessibility Structure
Read the accessibility tree and check labels, identifiers, and element locations during audits.
Try These Prompts
Use axe-ios-simulator to list available simulators and help me choose a UDID for testing.
Use AXe to tap Continue, type sample text, and take a screenshot in the selected simulator.
Describe the current simulator UI with AXe, summarize missing labels, and suggest safer selectors for automation.
Create an AXe command sequence that waits for a target element, scrolls until visible, fills a test form, records video, and captures a final screenshot.
Best Practices
- Use dedicated test simulators and test accounts before capturing screenshots or video.
- Prefer accessibility identifiers over coordinates when the app provides stable labels.
- Review each generated command before execution, especially install, file, and media commands.
Avoid
- Do not run capture commands on simulators that contain production data.
- Do not hard-code real passwords, tokens, or customer data in text input examples.
- Do not depend only on coordinates when labels or identifiers are available.