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 skills add simiancraft/simiancraft-skills --skill mobile-accessibilitygit clone --depth 1 https://github.com/simiancraft/simiancraft-skillsWrote 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/skills/simiancraft/simiancraft-skills/mobile-accessibility)<a href="https://agentmods.dev/skills/simiancraft/simiancraft-skills/mobile-accessibility"><img src="https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/mobile-accessibility/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/skills/simiancraft/simiancraft-skills/mobile-accessibility"><img src="https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/mobile-accessibility.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.00000 | $0.00879 |
| Opus 5 | $0.00000 | $0.00439 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
mobile-accessibility 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 12d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Accessibility (the shared trunk)
Why its own skill: the same tags serve two consumers (driving vs auditing); owning them here keeps both DRY. Driving skills read the handle; auditing skills read the semantics.
The model: one tree, two readers
An accessible app exposes an accessibility tree: a hierarchy of elements that assistive technology (VoiceOver) navigates, and that an automation driver (AXe) reads to find and tap things. Every element can carry a few fields. Two of them matter most, and they exist for different reasons:
| Field (iOS) | React Native prop | Who reads it | What it is for |
|---|---|---|---|
accessibilityIdentifier |
testID |
the driver | a stable handle to find an element in a script |
accessibilityLabel |
accessibilityLabel |
the human (VoiceOver) and the auditor | the element's name, spoken aloud |
Apple draws this line itself: an identifier lets a script "uniquely identify an element"
and thereby "avoid inappropriately setting or accessing an element's accessibility label"
(accessibilityIdentifier docs). React Native's testID is the same idea from the other
side: "Used to locate this view in end-to-end tests." The label, by contrast, is "a
string that succinctly identifies the accessibility element" for a user; Apple's example
is "Save," not "Save button."
So:
- Driving wants the handle. Prefer
testID->accessibilityIdentifier; it does not change when copy, locale, or layout changes. Tapping by visible label is the fallback when no handle exists. Coordinates are the last resort (brittle; see ios-simulatorreferences/driving.md). - Auditing wants the semantics: is there a label at all, is the role right, is the state (disabled, selected, checked) correct, is the focus order sane.
Where to go
- iOS-native fields and how they surface to a driver:
references/ios-native.md. - React Native / Expo props and the RN -> native mapping:
references/react-native-expo.md. - The auditing lens (completeness, correctness):
references/auditing.md.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 71 lines · 0 tokens per session scan A 91ba3c9ebb37
mobile-accessibility is a skill published in the GitHub repository simiancraft/simiancraft-skills (7 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 879 tokens. 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 skills, from other repositories
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…
validate-mobile
Run a Maestro flow on an explicitly selected iOS or Android device and report behavioral evidence.
swiftui-expert
This skill should be used when SwiftUI work requires judgment about Observation and state ownership, view identity or lifecycle, navigation, app-target concurrency, persistence, Apple-platform behavior, accessibility, performance, or architecture. Trigger on "review this SwiftUI screen", "why isn't this view…
swiftui-expert
This skill should be used when the user is building, reviewing, or debugging SwiftUI views and apps. Detects iOS and Swift version from the project. Covers creating views, state management with @Observable, NavigationStack routing, animations, accessibility, performance optimization, Liquid Glass adoption, design…
add-native
Public entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, PDF generation/viewing, pen/signature capture, background GPS/geolocation tracking, or supported local file workflows — in a Power Apps…
add-geolocation
Internal implementation skill invoked by /add-native for native background GPS tracking with durable storage and Dataverse sync using @microsoft/power-apps-native-bglocation.