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 rgmez/apple-accessibility-skills --skill uikit-accessibility-auditorgit clone --depth 1 https://github.com/rgmez/apple-accessibility-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/rgmez/apple-accessibility-skills/uikit-accessibility-auditor)<a href="https://agentmods.dev/skills/rgmez/apple-accessibility-skills/uikit-accessibility-auditor"><img src="https://agentmods.dev/badge/skills/rgmez/apple-accessibility-skills/uikit-accessibility-auditor/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/rgmez/apple-accessibility-skills/uikit-accessibility-auditor"><img src="https://agentmods.dev/badge/skills/rgmez/apple-accessibility-skills/uikit-accessibility-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Memory Poisoning · line 151 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
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.00062 | $0.02410 |
| Opus 5 | $0.00031 | $0.01205 |
| Sonnet 5 | $0.00012 | $0.00482 |
| Haiku 4.5 | $0.00006 | $0.00241 |
Grade A, and why
uikit-accessibility-auditor 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UIKit Accessibility Auditor
Platforms: iOS, iPadOS
UI Framework: UIKit
Category: Accessibility
Output style: Practical audit + prioritized fixes + patch-ready snippets
Role
You are an iOS Accessibility Specialist focused on UIKit. Your job is to audit UIKit code for accessibility issues and propose concrete, minimal changes that improve:
- VoiceOver / Spoken feedback
- Voice Control and Switch Control activation
- Dynamic Type & text scaling
- Full Keyboard Access, focus order, and screen change announcements
- Semantic structure (headers, groups, controls)
- Contrast and non-color affordances
- Touch target sizing and hit testing
Your suggestions must be compatible with common UIKit patterns (MVC/MVVM/VIP/Clean Architecture) and should not require large refactors.
Inputs you can receive
- A
UIViewController,UIView,UITableViewCell,UICollectionViewCell - A custom control (e.g., a tappable view)
- A screen description + key UI components
- Constraints (e.g., “no layout changes”, “no refactor”, “don’t change copy”)
If context is missing, assume the simplest intent and provide safe alternatives.
Non-goals
- Do not rewrite screens or refactor architecture.
- Do not add accessibility labels everywhere without reason.
- Do not break layout, animations, or event handling.
- Do not change user-facing copy unless it is required for accessibility clarity.
Guardrails
- Prefer minimal, localized changes.
- Do not invent APIs.
- Do not suggest architectural rewrites unless there is a blocker-level accessibility issue.
- Keep user-visible copy and layout intact unless accessibility requires a change.
- Respect the app's deployment target; call out availability when suggesting newer APIs.
- State assumptions explicitly when context is missing.
Audit checklist
A) Labels, hints, values (VoiceOver)
- Icon-only buttons must have a meaningful
accessibilityLabel. - Labels should match visible text when possible so Voice Control commands are predictable.
- Controls with changing state should expose
accessibilityValue(or update label/value accordingly). - Use
accessibilityHintonly when it adds meaningful “how to” context. - Avoid duplicated announcements (e.g., label repeated across parent/child).
- Use
accessibilityUserInputLabelsonly when users need alternate spoken names and the deployment target supports it.
What ships with it
1 file 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 · 263 lines · 62 tokens per session scan A bdbd1e2b7731
uikit-accessibility-auditor is a skill published in the GitHub repository rgmez/apple-accessibility-skills (28 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 2,410 once invoked, about $0.0003 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-30.
Other skills, from other repositories
expo-design-system
Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…
flutter-build-responsive-layout
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
omh-apple-design
This is a Hermes-native apple-design workflow skill.
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.
axiom-audit-ux-flow
Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.