A one-page accessibility audit. Accessibility means making a website usable by people who use screen readers, need strong text contrast, cannot distinguish some colours, or navigate with a keyboard.

Use it to check an important page such as a home page, checkout, or sign-up screen before sharing it.

It finds barriers that can stop people from using the page and explains which issues are most important. It also gives the page a grade from A to D.

ds-a11y — Skill for Claude Code and Codex by harshii0509: A one-page accessibility audit.

Install

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.

agentmods

npx agentmods add skills/harshii0509/designstack/a11y

Any agent

npx skills add harshii0509/designStack --skill a11y

Clone the repo

git clone --depth 1 https://github.com/harshii0509/designStack

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/harshii0509/designstack/a11y.svg)](https://agentmods.dev/skills/harshii0509/designstack/a11y)

Your own site

<a href="https://agentmods.dev/skills/harshii0509/designstack/a11y"><img src="https://agentmods.dev/badge/skills/harshii0509/designstack/a11y.svg" alt="Measured on agentmods" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,500 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00062	$0.02500
Opus 5	$0.00031	$0.01250
Sonnet 5	$0.00012	$0.00500
Haiku 4.5	$0.00006	$0.00250

Measured 4d ago against content hash fd6f5cb2dc42, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ds-a11y 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 4d 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.

a11y/SKILL.md · 288 lines

How it starts

The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Preamble

"../lib/env.sh" "a11y"

What accessibility means (explain this to the user if they haven't run `/ds-a11y` before)

"Accessibility means your website works for everyone — including people who are blind and use a screen reader to hear the page, people with low vision who need high contrast text, people who are color-blind, and people who use a keyboard instead of a mouse. Many countries also have legal requirements around this.

I'll check your site against the main rules and give you a grade from A to D, plus a screenshot showing exactly where each problem is."

This is a one-page accessibility audit. If the user wants a broader launch review, route them to /ds-polish instead.

Step 1 — Load Design Bible (if present)

If DESIGN_BIBLE is yes, follow the standard extraction protocol in lib/bible-reader.md. Focus on L1 Colors and L4 component rules for contrast checking.

Step 2 — Get the URL

Ask the user:

"What page should I check for accessibility? Give me the URL (e.g. http://localhost:3000 or your live URL). The home page is a good start, or try your most important page like checkout or signup."

Step 2 — Take a baseline screenshot

If BROWSE is not NOT_FOUND:

$B goto <URL>
$B screenshot /tmp/dstack-a11y-before.png

If the URL is not reachable:

"Your project doesn't seem to be running right now. Start it with npm run dev (or npm start) and then give me the URL — usually http://localhost:3000. I'll wait."

Do not continue until the user confirms the project is running.

Show the screenshot to the user:

"Here's your page. Let me run the accessibility check now."

Step 3 — Take screenshot and run accessibility audit

If BROWSE is not NOT_FOUND:

"../lib/visual-audit.sh" screenshot "<URL>" "a11y" "before"

If the URL is not reachable, run and show the output of:

"../lib/visual-audit.sh" not_running

Do not continue until the user confirms the project is running.

Read the full file on GitHub · 288 lines

Files

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.

references/axe-translation.md 3.1 KB

Changes

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.

4d ago First seen · 288 lines · 62 tokens per session scan A fd6f5cb2dc42

Subscribe to this mod's changes

ds-a11y is a skill published in the GitHub repository harshii0509/designStack (13 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 2,500 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.

Frontend Testing

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens