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.
git clone --depth 1 https://github.com/nyldn/claude-dolphinWrote 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/commands/nyldn/claude-dolphin/accessibility-check)<a href="https://agentmods.dev/commands/nyldn/claude-dolphin/accessibility-check"><img src="https://agentmods.dev/badge/commands/nyldn/claude-dolphin/accessibility-check/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/commands/nyldn/claude-dolphin/accessibility-check"><img src="https://agentmods.dev/badge/commands/nyldn/claude-dolphin/accessibility-check.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.00010 | $0.01625 |
| Opus 5.5 | $0.00004 | $0.00650 |
| Sonnet 5.5 | $0.00002 | $0.00325 |
| Haiku 4.5 | $0.00001 | $0.00162 |
Grade A, and why
accessibility-check 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 1mo 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Check Command
Perform focused WCAG 2.2 AA compliance audit on the specified component or file.
WCAG 2.2 AA Checklist
Read the target file and evaluate against each criterion below.
1. Perceivable
1.1 Text Alternatives
- 1.1.1 Non-text Content - All images have alt text
- Check:
<img>elements havealtattribute - Check: Icon buttons have aria-label or visible text
- Check: Decorative images have
alt=""
- Check:
1.3 Adaptable
-
1.3.1 Info and Relationships - Semantic structure
- Check: Headings use h1-h6 appropriately
- Check: Lists use ul/ol/dl
- Check: Tables have th headers
- Check: Forms have proper label associations
-
1.3.2 Meaningful Sequence - Reading order logical
- Check: DOM order matches visual order
1.4 Distinguishable
-
1.4.1 Use of Color - Color not sole indicator
- Check: Links have underline or other indicator
- Check: Errors not indicated by color alone
- Check: Required fields not indicated by color alone
-
1.4.3 Contrast (Minimum) - Text contrast ratios
- Check: Body text >= 4.5:1 against background
- Check: Large text (18px+) >= 3:1
- Check: Bold text (14px+) >= 3:1
-
1.4.11 Non-text Contrast - UI element contrast
- Check: Form inputs borders >= 3:1
- Check: Icons >= 3:1
- Check: Focus indicators >= 3:1
-
1.4.12 Text Spacing - Adjustable spacing
- Check: Content readable with 1.5x line height
- Check: No overflow with 2x paragraph spacing
2. Operable
2.1 Keyboard Accessible
-
2.1.1 Keyboard - All functionality via keyboard
- Check: Interactive elements have tabIndex or are native
- Check: onClick handlers have onKeyDown equivalents
- Check: Custom widgets support expected keys
-
2.1.2 No Keyboard Trap - Can navigate away
- Check: Focus can leave all components
- Check: Modals have escape key handler
2.4 Navigable
- 2.4.3 Focus Order - Logical focus sequence
- Check: tabIndex values are 0 or -1 (not positive)
- Check: Focus order matches visual layout
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.
- 1mo ago First seen · 204 lines · 10 tokens per session scan A abdb88990818
accessibility-check is a command published in the GitHub repository nyldn/claude-dolphin (8 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 1,625 once invoked, about $0.0000 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-31.
Other commands, from other repositories
style-guide
Generate a style guide with design tokens, type scale, spacing, components, and Tailwind or CSS config.
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
svg-create
Author or clean up an SVG asset — icon, illustration, mascot pose, logo mark — so it scales from viewBox, recolors from tokens, animates without a rewrite, is optimized, and has an accessible name.
agentation-fix
Session-2 fix loop for Agentation — read structured annotations from the dev overlay and apply targeted UI fixes.
scan-ai-tells
Scan UI or marketing copy for AI-default tells and content-authenticity misses — deletion list, not a redesign brief.
design-critic
Use when you want an honest read on a design instead of encouragement. What is wrong, ranked by severity, with the reason attached. Works on a screenshot, a mockup, or a described screen.