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 ilyasibrahim/claude-agents-coordination --skill accessibility-checklistgit clone --depth 1 https://github.com/ilyasibrahim/claude-agents-coordinationWrote 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/ilyasibrahim/claude-agents-coordination/accessibility-checklist)<a href="https://agentmods.dev/skills/ilyasibrahim/claude-agents-coordination/accessibility-checklist"><img src="https://agentmods.dev/badge/skills/ilyasibrahim/claude-agents-coordination/accessibility-checklist/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/ilyasibrahim/claude-agents-coordination/accessibility-checklist"><img src="https://agentmods.dev/badge/skills/ilyasibrahim/claude-agents-coordination/accessibility-checklist.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.00038 | $0.02153 |
| Opus 5.5 | $0.00015 | $0.00861 |
| Sonnet 5.5 | $0.00008 | $0.00431 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
accessibility-checklist 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 2mo 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Checklist (WCAG AA)
Keyboard Navigation
✅ Requirements
Tab Order:
- All interactive elements reachable via Tab
- Logical tab order (left-to-right, top-to-bottom)
- Skip links provided for repetitive navigation
- No keyboard traps
Interactive Elements:
- Buttons activate with Enter/Space
- Links activate with Enter
- Form inputs accessible via Tab
- Dropdowns navigable with Arrow keys
- Modals closable with Escape
Testing:
1. Unplug mouse
2. Navigate entire dashboard using only keyboard
3. Verify all features accessible
4. Check tab order is logical
Focus Indicators
✅ Requirements
Visibility:
- Focus indicators visible on ALL interactive elements
- Minimum 2px outline or 3px box-shadow
- Sufficient color contrast (3:1 minimum)
- Not removed with
outline: noneunless replaced
Implementation:
/* Good focus states */
.btn:focus-visible {
outline: 3px solid var(--tableau-blue);
outline-offset: 3px;
}
.data-toggle__option:focus-visible {
outline: 2px solid var(--data-blue-primary);
outline-offset: 2px;
z-index: 1;
}
/* Chart canvas focus */
canvas:focus-visible {
outline: 2px solid var(--data-cyan-primary);
outline-offset: 2px;
border-radius: 4px;
}
Color Contrast
✅ Requirements (WCAG AA)
Normal Text (< 18px):
- Minimum 4.5:1 contrast ratio
Large Text (≥ 18px or 14px bold):
- Minimum 3:1 contrast ratio
UI Components:
- Buttons: 3:1 minimum
- Form inputs: 3:1 border contrast
- Icons: 3:1 against background
Verified Combinations:
| Foreground | Background | Ratio | Status |
|---|---|---|---|
| White | Tableau Blue (#0176D3) | 4.83:1 | ✅ AA |
| White | Tableau Navy (#032D60) | 13.55:1 | ✅ AAA |
| Text (#333) | White | 12.63:1 | ✅ AAA |
| Data Cyan (#33BBEE) | White | 2.4:1 | ❌ (use dark text) |
Testing Tool:
- WebAIM Contrast Checker: https://webaim.org/resources/contrastchecker/
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.
- 2mo ago First seen · 386 lines · 38 tokens per session scan A 8cd4e1a49bdb
accessibility-checklist is a skill published in the GitHub repository ilyasibrahim/claude-agents-coordination (87 stars, last pushed 5mo ago), licensed Unlicense. It adds 38 tokens to every session and 2,153 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.