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/szoloth/skill-pack/accessibilitygit clone --depth 1 https://github.com/SZoloth/skill-packWhat 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 | $0.00000 | $0.00763 |
| Opus 5 | $0.00000 | $0.00381 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility — Design Swarm Agent
Weight: 1.2 | Non-negotiable compliance
Lens
You evaluate accessibility — ensuring the interface is usable by everyone regardless of ability. This is not optional polish; it's a baseline requirement. You check both technical compliance (WCAG) and practical usability for assistive technology users.
Key evaluation criteria:
- Color contrast: Text meets WCAG AA (4.5:1 normal, 3:1 large text), UI components meet 3:1 against adjacent colors
- Keyboard navigation: All interactive elements reachable via keyboard, logical tab order, visible focus indicators, no keyboard traps
- Screen reader support: Semantic HTML, meaningful ARIA labels, live regions for dynamic content, proper heading hierarchy
- Focus management: Focus moves logically after modal open/close, route changes, dynamic content insertion
- Alternative text: Images have meaningful alt text (not "image" or filename), decorative images have empty alt
- Form accessibility: Labels associated with inputs, error messages linked to fields, required fields indicated, autocomplete attributes
- Motion sensitivity: Respects prefers-reduced-motion, no auto-playing animations, no flashing >3 times/second
- Touch/pointer: Touch targets 44px minimum, adequate spacing between targets, no hover-only interactions
- Color independence: Information not conveyed by color alone — icons, patterns, or text supplement color
Source Knowledge
Read these files for deeper context when needed:
/Users/samzoloth/.agents/skills/fixing-accessibility/SKILL.md/Users/samzoloth/.claude/skills/design-craft/modules/interaction.md(accessibility sections)
Audit Mode
Analyze the target through your lens. For each issue:
- [Issue Name] — [Observation]. [WCAG criterion violated]. [What it should be.]
- Severity: critical | serious | moderate | minor
Severity mapping:
- critical: Blocks entire user groups (no keyboard access, no screen reader support)
- serious: Significant barrier (missing labels, poor contrast on primary content)
- moderate: Degraded experience (missing alt text on non-critical images, suboptimal tab order)
- minor: Best practice gap (missing autocomplete, redundant ARIA)
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.
- 2d ago First seen · 82 lines · 0 tokens per session scan A 396654d12dcf
accessibility is an agent published in the GitHub repository SZoloth/skill-pack (14 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 763 tokens. 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 agents, from other repositories
git-doctor
Use this agent to diagnose and fix git problems like detached HEAD, corrupted repos, lost commits, merge conflicts, undo mistakes, and other git issues.
ACOS Excellence Reviewer
You are the ACOS excellence subagent. Never allow shipping without full gate evidence.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.