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 vasilyu1983/AI-Agents-public --skill software-accessibilitygit clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicWrote 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/vasilyu1983/ai-agents-public/software-accessibility)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/software-accessibility"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/software-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/vasilyu1983/ai-agents-public/software-accessibility"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/software-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.03171 |
| Opus 5.5 | $0.00013 | $0.01268 |
| Sonnet 5.5 | $0.00006 | $0.00634 |
| Haiku 4.5 | $0.00003 | $0.00317 |
Grade A, and why
software-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 20d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Engineering
This skill owns engineering implementation. It does not own design-side WCAG interpretation or formal accessibility-test programs.
Quick Reference
| Need | Default | Notes |
|---|---|---|
| fix component semantics | semantic HTML first | add ARIA only when HTML is insufficient |
| keyboard support | tab order, visible focus, correct key handling | test manually every time |
| screen reader verification | Primary browser/reader pair for the affected users | add a second platform for shared primitives or cross-platform claims |
| automated coverage | axe-core plus Lighthouse or Pa11y | automation catches markup-level issues, not the full experience |
| modal or composite widget | APG-aligned pattern | do not invent custom keyboard behavior |
| compliance prep | Design/test to WCAG 2.2 AA, then map the applicable legal or procurement baseline | do not describe the design target as the binding version everywhere |
| WCAG 2.2 checklist, axe-core/Pa11y snippets, EU Accessibility Act | references/wcag-2-2-checklist.md | technical mapping only; EAA applicability goes to qualified counsel |
| run axe-core in CI | scripts/run_axe.sh | exits non-zero on violations |
When to Use This Skill
Use this skill when the main work is:
- remediating semantic HTML, labels, roles, and landmarks
- fixing keyboard access, focus management, or SPA route focus behavior
- implementing APG-style component patterns
- improving screen-reader announcements and dynamic content handling
- adding accessibility engineering checks to CI
Route elsewhere when the main work is:
| Need | Use Instead |
|---|---|
| design-side accessibility and interaction design | ../software-ui-ux-design/SKILL.md |
| accessibility test automation program or formal audit flow | ../qa-testing-accessibility/SKILL.md |
| usability research with disabled users | ../software-ux-research/SKILL.md |
| frontend stack setup and general UI build work | ../software-frontend/SKILL.md |
| platform-specific mobile accessibility behavior | ../software-mobile/SKILL.md |
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 289 B
- data/sources.json 7.5 KB
- evals/evals.json 9.8 KB
- learnings.consolidated.md 598 B
- learnings.md 643 B
- references/regulatory-traps.md 3.3 KB
- references/remediation-playbook.md 8.2 KB
- references/wcag-2-2-checklist.md 4.8 KB
- references/wcag-2.2-and-3.0-watchlist.md 14 KB
- scripts/check_a11y_baseline.py 11 KB runs code
- scripts/run_axe.sh 2.6 KB runs code
- scripts/test_a11y_regressions.py 4.6 KB runs code
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.
- 20d ago Changed · -93 lines d97fcf0967db
- 1mo ago Changed · +5 lines 99f2c589d1d3
- 1mo ago First seen · 319 lines · 32 tokens per session scan A b77dd5fb639c
software-accessibility is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (101 stars, last pushed 10d ago), licensed MIT. It adds 32 tokens to every session and 3,171 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
brand-landingpage
Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established…
qa-design
UI/UX design audit and verification of web best practices, including responsive/mobile-first breakpoints. Trigger when the user wants to audit the design, verify the UI/UX, check responsive behaviour, or improve the user interface.
dev-frontend-design
Distinctive UI design with strong art direction. Trigger when the user wants to create an interface, a landing page, a visual component, or when frontend code creation is detected without a defined design direction.
dev-shadcn
Integration and customization of shadcn/ui (copy-paste React components, Radix + Tailwind). Trigger when the user wants to install shadcn, add components, customize the theme, or when shadcn/ui usage is detected in the project.
design-system
DESIGN.md integration for Forge — ensures visual consistency across all UI tasks through standardized design specifications.
aetox-shadcn
ทำงานกับ shadcn/ui, เพิ่ม ค้น แก้ ดีบัก สไตล์ และประกอบคอมโพเนนต์/ดีไซน์ซิสเทม ผ่าน registry และ CLI พร้อมกฎที่บังคับเสมอ (className สำหรับ layout ไม่ใช่สไตล์, ใช้ gap ไม่ใช่ space-x/y, size- เมื่อกว้างเท่าสูง, semantic colors, cn()) ใช้ตอนโปรเจกต์มี components.json หรือทำงานกับ shadcn/Tailwind/Base UI, "shadcn init"…