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 kumaran-is/claude-code-onboarding --skill accessibility-auditgit clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/accessibility-audit)<a href="https://agentmods.dev/skills/kumaran-is/claude-code-onboarding/accessibility-audit"><img src="https://agentmods.dev/badge/skills/kumaran-is/claude-code-onboarding/accessibility-audit/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/kumaran-is/claude-code-onboarding/accessibility-audit"><img src="https://agentmods.dev/badge/skills/kumaran-is/claude-code-onboarding/accessibility-audit.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.00072 | $0.01119 |
| Opus 5.5 | $0.00029 | $0.00448 |
| Sonnet 5.5 | $0.00014 | $0.00224 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
accessibility-audit 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Audit
Iron Law: Before auditing any component, READ the actual file first. Do not flag violations based on memory — verify at file:line and show evidence.
WCAG 2.1 AA compliance audit for Angular 21.x and Flutter 3.41.x. Use to audit UI components, establish automated testing, identify accessibility barriers, and prepare compliance evidence.
When to Use
- Auditing Angular or Flutter UI for WCAG 2.1 AA compliance
- Adding automated accessibility tests to CI/CD
- Identifying and remediating accessibility barriers
- Preparing compliance evidence for stakeholders
- Reviewing a PR that adds UI components
Do Not Use
- For general UI design review without accessibility scope
- For backend services with no UI (Java, NestJS, Python, FastAPI)
- When you cannot access the UI files or artifacts
Process
- Confirm scope — which components, pages, or user journeys to audit
- Run automated scan — axe-core (Angular) or flutter_test semantics (Flutter) for baseline violations
- Perform manual checks — keyboard, screen reader, focus order, contrast
- Map findings to WCAG criteria — severity (Critical / Important / Suggestion) and WCAG criterion
- Provide remediation — exact code fixes with file:line evidence
- Re-test after fixes — confirm each finding is resolved
Reference Files
| File | Contents | Load When |
|---|---|---|
reference/angular-a11y-automated.md |
axe-core Angular integration, keyboard trap detection, heading structure validation, pa11y | Adding automated a11y tests to Angular project |
reference/flutter-a11y-automated.md |
flutter_test semantics testing, SemanticsController patterns, widget test accessibility | Adding automated a11y tests to Flutter project |
reference/manual-testing-checklist.md |
Keyboard, screen reader, visual, cognitive manual checklists for both stacks | Running manual audit session |
reference/cicd-integration.md |
GitHub Actions workflows for Angular (axe + pa11y) and Flutter (semantic tests) | Integrating a11y into CI/CD pipeline |
What ships with it
4 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.
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 · 99 lines · 72 tokens per session scan A 8701f0389e2c
accessibility-audit is a skill published in the GitHub repository kumaran-is/claude-code-onboarding (36 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 1,119 once invoked, about $0.0003 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
tdd
Guided test-driven development workflow for .NET 10 using xUnit v3, WebApplicationFactory, Testcontainers, and Verify snapshots. Follows the strict red-green-refactor cycle. Use when: "TDD", "test-driven", "let's TDD this", "red green refactor", "write the test first", or when building a feature with clear acceptance…