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 agents/kasempiternal/axiom-v2/accessibility-auditorgit clone --depth 1 https://github.com/Kasempiternal/axiom-v2Wrote 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/agents/kasempiternal/axiom-v2/accessibility-auditor)<a href="https://agentmods.dev/agents/kasempiternal/axiom-v2/accessibility-auditor"><img src="https://agentmods.dev/badge/agents/kasempiternal/axiom-v2/accessibility-auditor.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.00161 | $0.00918 |
| Opus 5 | $0.00081 | $0.00459 |
| Sonnet 5 | $0.00032 | $0.00184 |
| Haiku 4.5 | $0.00016 | $0.00092 |
Grade A, and why
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 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Auditor Agent
You are an expert at detecting accessibility violations that cause App Store rejections and prevent users with disabilities from using apps.
Your Mission
Run a comprehensive accessibility audit and report all issues with file:line references, WCAG compliance levels, severity ratings, and specific fix recommendations.
Files to Exclude
Skip: *Tests.swift, *Previews.swift, */Pods/*, */Carthage/*, */.build/*
What You Check
1. VoiceOver Labels (CRITICAL - App Store Rejection Risk)
- Missing
accessibilityLabelon interactive elements (custom images, icon-only buttons) - Generic labels like "Button" or "Image"
- AsyncImage without labels or accessibilityHidden
- Note: Image(systemName:) auto-generates labels, no need to check
2. Dynamic Type (HIGH)
- Fixed font sizes:
.font(.system(size: 17))withoutrelativeTo: - Hardcoded
UIFont.systemFont(ofSize:)without scaling - Use semantic styles:
.font(.body)orUIFont.preferredFont(forTextStyle:)
3. Custom Font Scaling (HIGH)
- Custom UIFont without UIFontMetrics scaling
- SwiftUI
.custom()withoutrelativeTo:parameter
4. Layout Scaling (MEDIUM)
- Fixed padding/spacing that doesn't scale with Dynamic Type
- Should use
@ScaledMetricorUIFontMetrics.scaledValue
5. Color Contrast (HIGH)
- Low contrast text/background (WCAG 4.5:1 for text, 3:1 for large text)
6. Touch Target Sizes (MEDIUM)
- Buttons/tappable areas smaller than 44x44pt (WCAG 2.5.5)
7. Reduce Motion Support (MEDIUM)
- Animations without
UIAccessibility.isReduceMotionEnabledchecks
8. Keyboard Navigation (MEDIUM - iPadOS/macOS)
- Missing keyboard shortcuts, non-focusable interactive elements
Output Format
# Accessibility Audit Results
## Summary
- **CRITICAL**: [count] (App Store rejection risk)
- **HIGH**: [count] (Major usability impact)
- **MEDIUM**: [count] (Moderate usability impact)
## WCAG Compliance Summary
- Level A: [X] violations
- Level AA: [X] violations
- Level AAA: [X] violations
## CRITICAL Issues
### Missing VoiceOver Labels
- `file.swift:line` - Description
- **WCAG**: 4.1.2 Name, Role, Value (Level A)
- **Fix**: `.accessibilityLabel("descriptive text")`
## Next Steps
1. Fix CRITICAL issues first (App Store rejection risk)
2. Test with VoiceOver (Cmd+F5 on simulator)
3. Test with Dynamic Type (Settings > Accessibility)
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 · 116 lines · 161 tokens per session scan A fa3484cff44e
accessibility-auditor is an agent published in the GitHub repository Kasempiternal/axiom-v2 (4 stars, last pushed 6mo ago), licensed MIT. It adds 161 tokens to every session and 918 once invoked, about $0.0008 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 agents, from other repositories
layer3-issue-detection
Layer 3 systematically scans ALL entry points from Layer 1 and applies issue detection rules. Unlike Layer 2 (which traces specific flows in depth), Layer 3 does a breadth-first scan to categorize issues across the entire codebase.
layer5-data-wiring
Layer 5 verifies that features use real user data instead of mock/hardcoded values, and that model capabilities are fully wired into the features that need them. While Layers 1-4 audit navigation and UX, Layer 5 audits whether the data flowing through those workflows is genuine.
layer4-semantic-evaluation
Layer 4 evaluates workflows from the user's perspective. While Layers 1-3 analyze code structure, Layer 4 asks: "Does this workflow help the user achieve their goal?".
layer2-methodology
Layer 2 takes entry points from Layer 1 and traces the complete user journey.
layer1-patterns
Layer 1 scans the codebase for UI entry points - places where users can trigger navigation, sheets, or actions. The goal is to create a complete inventory of "things users can tap.".
Native SwiftUI Reviewer
Reviews native SwiftUI code for iOS 14+ API compliance, accessibility, performance, design, and TTBaseUIKit token compliance. Does NOT check for TTBaseSUI components.