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 Omar-Obando/qwen-orchestrator --skill accessibility-implementationgit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/accessibility-implementation)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/accessibility-implementation"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/accessibility-implementation.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.00061 | $0.02409 |
| Opus 5 | $0.00030 | $0.01205 |
| Sonnet 5 | $0.00012 | $0.00482 |
| Haiku 4.5 | $0.00006 | $0.00241 |
Grade A, and why
accessibility-implementation 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Implementation Skill — Frontend Developer
Overview
This skill provides comprehensive guidance for implementing accessible web content following WCAG 2.1 AA standards. It covers semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and accessibility testing following CPACC certification standards.
When to Use
Use this skill when:
- Implementing accessible web interfaces
- Ensuring WCAG 2.1 AA compliance
- Adding ARIA attributes to components
- Implementing keyboard navigation
- Testing with screen readers
- Creating accessible forms
- Implementing accessible tables
- Adding accessible color contrast
- Creating accessible navigation
- Implementing accessible modal dialogs
- Creating accessible charts and graphs
- Ensuring accessible error messages
- Implementing accessible focus management
- Creating accessible landing pages
- Testing with accessibility tools
- Conducting accessibility audits
- Implementing skip navigation links
- Creating accessible PDFs
- Ensuring accessible video content
- Implementing accessible print styles
- Creating accessible email templates
- Implementing accessible mobile interfaces
- Ensuring accessible dark mode
Do NOT use this skill when:
- Writing backend business logic (use domain-driven skill)
- Designing database schemas (use database-design skill)
- Writing API endpoint specifications (use api-design skill)
- Performing security audits (use security-auditor skill)
- Writing SQL queries (use sql-best-practices skill)
- Designing multi-page website layouts (use design-system skill)
- Analyzing deployment configurations (use deployment skill)
- Writing documentation (use documentation-best-practices skill)
WCAG 2.1 AA Principles
Perceivable
┌─────────────────────────────────────────────────────────────┐
│ Perceivable Principles │
├─────────────────────────────────────────────────────────────┤
│ 1.1 Text Alternatives - Provide text alternatives for │
│ non-text content │
│ 1.2 Time-based Media - Provide alternatives for time-based │
│ media │
│ 1.3 Adaptable - Create content that can be presented in │
│ different ways without losing meaning │
│ 1.4 Distinguishable - Make it easier for users to see and │
│ hear content │
└─────────────────────────────────────────────────────────────┘
What ships with it
1 file 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.
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 · 354 lines · 61 tokens per session scan A 462254d2e974
accessibility-implementation is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (48 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 2,409 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
frontend-expert
Expert skill for creating premium, high-performance Cyberpunk-themed UIs with Next.js and Tailwind.
ui-visual-match-replicator
A screenshot-driven workflow for rebuilding a webpage or frontend so its rendered appearance matches a supplied visual. It compares screenshots, identifies the largest differences, and repeats the implementation and correction cycle.
frontend-ui-engineering
Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".