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.
git 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/commands/yusufkaran/swiftui-autotest-skill/add-accessibility)<a href="https://agentmods.dev/commands/yusufkaran/swiftui-autotest-skill/add-accessibility"><img src="https://agentmods.dev/badge/commands/yusufkaran/swiftui-autotest-skill/add-accessibility.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.00053 | $0.01669 |
| Opus 5 | $0.00026 | $0.00834 |
| Sonnet 5 | $0.00011 | $0.00334 |
| Haiku 4.5 | $0.00005 | $0.00167 |
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 8d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Command: Add Accessibility
Bu komut SwiftUI dosyalarini tarayarak eksik accessibility identifier'lari otomatik ekler ve Dynamic Type uyumsuzluklarini raporlar.
Usage
/add-accessibility
/add-accessibility --dry-run
/add-accessibility --path=Sources/Features/Login
/add-accessibility --verbose
Command Options
--dry-run: Degisiklik yapma, sadece ne yapilacagini raporla--path=<path>: Sadece belirtilen dizini tara (varsayilan: tum SwiftUI dosyalari)--verbose: Her eklenen identifier'i detayli logla
What This Command Does
Phase 1: Scan & Analyze
-
Projedeki tum
*.swiftdosyalarini bul -
SwiftUI view'leri iceren dosyalari filtrele (struct X: View, #Preview, vb.)
-
Her dosyada su elemanlari tespit et:
Button- butonlarTextFieldveSecureField- input alanlariImage- gorsellerToggle- toggle switch'lerSlider- slider'larPicker- picker'larDatePicker- tarih secicilerNavigationLink- navigasyon linkleriTabViewicindeki tab item'lar.onTapGestureolan view'lar - tap gesture'lu elemanlarLink- harici link'ler
-
Her eleman icin mevcut accessibility durumunu kontrol et:
.accessibilityIdentifier()var mi?.accessibilityLabel()var mi?- Eger varsa → ATLA, dokunma
Phase 2: Generate Identifiers
Naming convention: {screen}-{type}-{name}
Screen ismi: Dosya adindan turet
LoginView.swift→loginOnboardingStepView.swift→onboarding-stepHomeTabView.swift→home-tabViewsuffix'ini kaldir, camelCase'i kebab-case'e cevir
Type: Eleman turune gore
| 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 |
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.
- 8d ago First seen · 193 lines · 0 tokens per session scan A 9174124eccf5
add-accessibility is a command published in the GitHub repository yusufkaran/swiftui-autotest-skill (24 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 1,669 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 commands, from other repositories
mobile-specialist
Use when a design will be used on phones. Touch targets too small, controls outside thumb reach, bottom navigation, gestures, safe areas and notches, or behaviour with no connection.
hig-scaffold
Generate a HIG-compliant component or screen for a chosen Apple platform and stack (SwiftUI, UIKit, React Native, Flutter, HTML/CSS, etc.), using the on-disk Apple guidelines.
audit
Run a full UI/UX design audit on the current project. Scores 12 dimensions and produces a markdown report with prioritized findings.
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
design-enforce
Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.
design-grill
Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.