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 djscheuf/agentic-dev-ecosystem-template --skill accessible-component-designgit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWrote 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/djscheuf/agentic-dev-ecosystem-template/accessible-component-design)<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/accessible-component-design"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/accessible-component-design/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/djscheuf/agentic-dev-ecosystem-template/accessible-component-design"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/accessible-component-design.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.04640 |
| Opus 5.5 | $0.00020 | $0.01856 |
| Sonnet 5.5 | $0.00010 | $0.00928 |
| Haiku 4.5 | $0.00005 | $0.00464 |
Grade A, and why
Accessible Component Design 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 21d 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 — 672 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessible Component Design Workflow
Systematic procedure for designing and implementing accessible UI components that meet WCAG 2.2 Level AA standards.
Overview
This skill guides you through creating accessible components by:
- Identifying the appropriate pattern
- Starting with semantic HTML
- Implementing keyboard navigation
- Adding ARIA only when necessary
- Managing focus properly
- Providing accessible names
- Testing thoroughly
Step 1: Identify Component Type
Goal: Determine if component matches an established W3C ARIA Authoring Practices Guide (APG) pattern.
Check APG Patterns First
Reference apg-patterns-reference.md for complete catalog of established patterns.
Common Patterns:
- Modal Dialog - Overlay that requires user interaction before returning to main content
- Tabs - Layered sections of content, only one visible at a time
- Accordion - Vertically stacked expandable/collapsible sections
- Menu/Menubar - Application menu with keyboard shortcuts
- Combobox - Input with autocomplete/search and popup listbox
- Radio Group - Set of mutually exclusive options
- Listbox - Selectable list of options (alternative to native select)
- Grid - Interactive table with cell-by-cell navigation
- Tree View - Hierarchical list with expand/collapse
Decision Tree
Does W3C APG have a pattern for this component?
├─ Yes → Follow APG pattern exactly (see apg-patterns-reference.md)
└─ No → Can this be simplified to use an existing pattern?
├─ Yes → Simplify design, use existing pattern
└─ No → Design custom pattern, test extensively
ShadCN/Radix Check
Before implementing custom component, check if ShadCN/Radix has it:
- Dialog/Modal
- Select/Combobox
- Tabs
- Accordion
- Dropdown Menu
- Popover
- Tooltip
If available, use ShadCN/Radix component (handles accessibility automatically).
Step 2: Start with Semantic HTML
Goal: Use native HTML elements that provide built-in accessibility.
What ships with it
7 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.
- apg-patterns-reference.md 15 KB
- aria-naming-hierarchy.md 13 KB
- component-examples/accessible-form-example.tsx 7.0 KB
- component-examples/custom-select-example.tsx 7.6 KB
- component-examples/modal-dialog-example.tsx 3.8 KB
- component-examples/tabs-example.tsx 4.6 KB
- keyboard-navigation-checklist.md 14 KB
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.
- 21d ago First seen · 672 lines · 49 tokens per session scan A 3dc933d61a7e
Accessible Component Design is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 20d ago), licensed MIT. It adds 49 tokens to every session and 4,640 once invoked, about $0.0002 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-10-02.
Other skills, from other repositories
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.