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 yusufkaran/swiftui-autotest-skill --skill add-accessibilitygit clone --depth 1 https://github.com/yusufkaran/swiftui-autotest-skillWrote 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/yusufkaran/swiftui-autotest-skill/add-accessibility)<a href="https://agentmods.dev/skills/yusufkaran/swiftui-autotest-skill/add-accessibility"><img src="https://agentmods.dev/badge/skills/yusufkaran/swiftui-autotest-skill/add-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/yusufkaran/swiftui-autotest-skill/add-accessibility"><img src="https://agentmods.dev/badge/skills/yusufkaran/swiftui-autotest-skill/add-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.00058 | $0.01432 |
| Opus 5 | $0.00029 | $0.00716 |
| Sonnet 5 | $0.00012 | $0.00286 |
| Haiku 4.5 | $0.00006 | $0.00143 |
Grade A, and why
add-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 9d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Accessibility Skill
Overview
Use this skill to scan all SwiftUI files in a project, find interactive elements missing accessibility identifiers, and add them using a consistent {screen}-{type}-{name} naming convention. Also flags Dynamic Type compatibility issues without auto-fixing them.
Options
--dry-run: Don't modify files, only report what would be changed--path=<path>: Scan only the specified directory (default: all SwiftUI files)--verbose: Log each identifier added in detail
Workflow
1) Scan & Analyze
-
Find all
*.swiftfiles in the project -
Filter to files containing SwiftUI views (
struct X: View,#Preview, etc.) -
In each file, detect these interactive elements:
Button— buttonsTextFieldandSecureField— input fieldsImage— imagesToggle— toggle switchesSlider— slidersPicker— pickersDatePicker— date pickersNavigationLink— navigation linksTabViewtab items.onTapGestureviews — tap gesture elementsLink— external links
-
For each element, check existing accessibility state:
- Has
.accessibilityIdentifier()? → SKIP - Has
.accessibilityLabel()? → SKIP - If either exists, do not touch it
- Has
2) Generate Identifiers
Naming convention: {screen}-{type}-{name}
Screen name: derived from the filename
LoginView.swift→loginOnboardingStepView.swift→onboarding-stepHomeTabView.swift→home-tab- Remove
Viewsuffix, convert camelCase to kebab-case
Type: based on the element type
| SwiftUI Element | Type |
|---|---|
| Button | button |
| TextField | textfield |
| SecureField | securefield |
| Image | image |
| Toggle | toggle |
| Slider | slider |
| Picker | picker |
| DatePicker | datepicker |
| NavigationLink | navlink |
| Link | link |
| .onTapGesture view | tap |
| TabView item | tab |
Name: derived from the element's content
Button("Continue")→continueTextField("Email", ...)→emailImage(systemName: "gear")→gearImage("hero-banner")→hero-bannerToggle("Notifications", ...)→notifications- No content or too complex → number sequentially (
button-1,button-2)
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.
- 9d ago First seen · 187 lines · 58 tokens per session scan A 7615d6701aeb
add-accessibility is a skill published in the GitHub repository yusufkaran/swiftui-autotest-skill (24 stars, last pushed 5mo ago), licensed MIT. It adds 58 tokens to every session and 1,432 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
iOS SwiftUI Accessibility
Enforces WCAG 2.2 accessible coding patterns when writing SwiftUI — labels, traits, Dynamic Type, contrast, touch targets, focus management, orientation, and more. Based on the ios-swiftui-accessibility-techniques project with 41 static analysis rules across 23 WCAG criteria.
uikit-expert
Write, review, or improve UIKit code following best practices for view controller lifecycle, Auto Layout, collection views, navigation, animation, memory management, and modern iOS 18–26 APIs. Use when building new UIKit features, refactoring existing views or view controllers, reviewing code quality, adopting modern…
apple-hig-ux
Apple-platform design and UX judgment — what a good iOS/iPadOS/macOS/watchOS/visionOS app FEELS like. Use whenever designing app screens or flows, answering Human Interface Guidelines (HIG) questions, judging "does this feel native", running a UX review of an Apple-platform app, choosing navigation patterns (tabs vs…
ios-design-agent-skill
Audit and improve iOS/SwiftUI app aesthetics — typography, color, spatial composition, motion, and atmospheric depth. Use when reviewing UI design, critiquing screenshots, or improving SwiftUI view code beyond functional correctness.
ax-design-ref
Design API reference -- HIG color/background/material system, typography (San Francisco, text styles, Dynamic Type, tracking, leading), SF Symbols complete API (rendering modes, effects, UIKit equivalents, platform matrix), Liquid Glass adoption guide (controls, navigation, windows, icons, migration), accessibility…
ax-design
Apple Human Interface Guidelines and SF Symbols -- design decisions, rendering modes, symbol effects/animations, Draw animations (iOS 26), accessibility compliance, and defending HIG decisions in design reviews.