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 Akakaui/visual-browser-agent --skill accessibility-reviewgit clone --depth 1 https://github.com/Akakaui/visual-browser-agentWrote 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/akakaui/visual-browser-agent/accessibility-review)<a href="https://agentmods.dev/skills/akakaui/visual-browser-agent/accessibility-review"><img src="https://agentmods.dev/badge/skills/akakaui/visual-browser-agent/accessibility-review.svg" alt="Measured on agentmods" 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.00030 | $0.00799 |
| Opus 5 | $0.00015 | $0.00400 |
| Sonnet 5 | $0.00006 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
accessibility-review 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 7d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Review Skill
When to Use
Use this skill to audit accessibility of the current page:
- Missing accessible names on interactive elements
- Broken or skipped heading hierarchy
- Unlabeled form controls
- Contrast, focus visibility, clipping, or overflow problems
- Pre-merge a11y spot checks or full page audits
Instructions
Tree Checks (via inspect_page)
Inspect the structured accessibility tree for:
- Missing accessible names: icon-only buttons, image links, links whose text is only an icon glyph
- Heading hierarchy: skipped levels (h2 -> h4), multiple h1s, headings used purely for visual styling
- Unlabeled controls: inputs without label text,
aria-label, oraria-labelledby; placeholders doing a label's job - Landmarks and roles: missing main/nav landmarks, incorrect ARIA roles, duplicate IDs referenced by labels
Screenshot Checks (capture_screenshot + review_visual_evidence)
Some failures only exist visually - screenshots are required:
- Contrast: text vs background ratios; flag below 4.5:1 normal text, 3:1 large text
- Focus visibility: tab through interactive elements and screenshot each focused state; flag invisible indicators
- Clipping: truncated or cut-off text at common viewports
- Overflow: content escaping containers, horizontal scroll traps, overlapping hit targets
Combining Evidence into Findings
Each finding pairs both evidence types where possible:
- Element selector/name from the tree + artifact ID of the supporting screenshot
- Format:
{element, issue, wcag, severity, confidence, evidence[]} - Tree-only findings still get a context screenshot when feasible
WCAG References
| Issue | WCAG 2.x Success Criterion |
|---|---|
| Missing accessible name | 4.1.2 Name, Role, Value |
| Heading hierarchy broken | 1.3.1 Info and Relationships |
| Unlabeled input | 3.3.2 Labels or Instructions |
| Low contrast | 1.4.3 Contrast (Minimum) |
| Invisible focus indicator | 2.4.7 Focus Visible |
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.
- 7d ago First seen · 84 lines · 30 tokens per session scan A f9c87d744ad5
accessibility-review is a skill published in the GitHub repository Akakaui/visual-browser-agent (0 stars, last pushed 13d ago), licensed MIT. It adds 30 tokens to every session and 799 once invoked, about $0.0002 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-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…