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 skills/desquared/agents-rules-skills/ios-accessibility-validatornpx skills add Desquared/agents-rules-skills --skill ios-accessibility-validatorgit clone --depth 1 https://github.com/Desquared/agents-rules-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/desquared/agents-rules-skills/ios-accessibility-validator)<a href="https://agentmods.dev/skills/desquared/agents-rules-skills/ios-accessibility-validator"><img src="https://agentmods.dev/badge/skills/desquared/agents-rules-skills/ios-accessibility-validator.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.00050 | $0.01549 |
| Opus 5 | $0.00025 | $0.00775 |
| Sonnet 5 | $0.00010 | $0.00310 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
ios-accessibility-validator 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Validator
Core Checklist (applies to most projects)
VoiceOver & Screen Reader
- Interactive elements have
.accessibilityLabel()or meaningful built-in label - Decorative / purely visual elements use
.accessibilityHidden(true) - Related elements grouped with
.accessibilityElement(children: .combine)or.accessibilityElement(children: .contain) - Complex controls provide
.accessibilityHint()when label alone is insufficient - Appropriate
.accessibilityTraits(.button,.header,.image,.adjustable,.toggle, etc.) - Stateful controls provide
.accessibilityValue()(e.g., "50%", "3 of 10", "On") - Custom gestures have equivalent
.accessibilityAction()alternatives - Labels & hints are localized (use
LocalizedStringKeyorNSLocalizedString) - Use
.accessibilityRotor()to provide quick navigation for repeated content types (feeds, search results, settings)
Dynamic Type & Text Scaling
- Use semantic font styles (
.font(.body),.headline,.title, etc.) — avoid.system(size:) - Support at least 200% text scaling without truncation, overlap, or horizontal scrolling
- Use
@ScaledMetricor.dynamicTypeSizemodifiers for padding, spacing, icon sizes - Layout adapts gracefully to largest Dynamic Type sizes (use
.minimumScaleFactorsparingly) - Use
ViewThatFitsto provide alternative layouts at extreme Dynamic Type sizes (e.g., vertical instead of horizontal)
Color & Visual Indicators
- Text contrast ≥ 4.5:1 (normal), ≥ 3:1 for large/bold text (≥18 pt bold or ≥24 pt regular)
- Use semantic colors (
.primary,.secondary,.accentColor,.fill) over hardcoded colors - Color is not the only way information is conveyed (use icons, patterns, text too)
- Test with both light and dark appearance — ensure contrast holds in both
- Support Increase Contrast setting (
.accessibilityContrastenvironment value) with higher-contrast color variants
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 · 153 lines · 50 tokens per session scan A 14b118143f95
ios-accessibility-validator is a skill published in the GitHub repository Desquared/agents-rules-skills (4 stars, last pushed 23d ago), licensed MIT. It adds 50 tokens to every session and 1,549 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-31.
Other skills, from other repositories
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…
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.
platform-conventions
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).
field-service-mobile-branding-configure
Derive a Field Service mobile app color scheme from a brand source (URL, hex codes, brand-guide paste, or color description), validate WCAG AA contrast in both light and dark mode, and apply the 14-field scheme to the org-default FieldServiceMobileSettings record. Trigger phrases include 'brand the mobile app', 'apply…
app-ui-design
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.