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 dr-robert-li/cowork-wordpress-expert --skill accessibilitygit clone --depth 1 https://github.com/dr-robert-li/cowork-wordpress-expertWrote 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/dr-robert-li/cowork-wordpress-expert/accessibility)<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/accessibility"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/accessibility.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.00031 | $0.02375 |
| Opus 5 | $0.00015 | $0.01188 |
| Sonnet 5 | $0.00006 | $0.00475 |
| Haiku 4.5 | $0.00003 | $0.00237 |
Grade A, and why
accessibility 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 8d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility & Compliance
WCAG Compliance
Heading Hierarchy
- Proper semantic heading structure (h1 → h2 → h3, no skipping levels)
- Only one h1 per page (typically the page title)
- Headings used for structure, not styling (no "heading because it looks bold")
- Theme templates follow logical heading progression
- Page builders don't break heading hierarchy with out-of-order elements
- Skip links provided for keyboard navigation to main content
- Landmark regions properly defined (header, nav, main, aside, footer)
Image Accessibility
- All content images have descriptive alt text
- Decorative images have empty alt attribute (
alt="") - Complex images (charts, diagrams) have longer descriptions via aria-describedby or adjacent text
- Image upload interfaces prompt for alt text
- Featured images have alt text handling
- CSS background images not used for content (only decoration)
- SVG images include title and desc elements where appropriate
Form Accessibility
- Every form input has an associated label (explicit with
forattribute or implicit wrapping) - Required fields indicated both visually and semantically (aria-required="true")
- Error messages associated with inputs via aria-describedby
- Fieldsets and legends used for grouped form controls (radio buttons, checkboxes)
- Placeholder text not used as the only label (placeholders disappear on input)
- Focus states clearly visible on all interactive elements
- Form validation provides clear, specific error messages
- Submit buttons have descriptive text (not just "Submit" or "Go")
Color and Contrast
- Text color contrast ratios meet WCAG AA standards:
- Normal text: 4.5:1 minimum
- Large text (18pt+/14pt+ bold): 3:1 minimum
- AAA standards: 7:1 for normal, 4.5:1 for large
- Color not used as the only means of conveying information
- Link text distinguishable from surrounding text (underline, icon, or sufficient contrast difference)
- Focus indicators have sufficient contrast (3:1 minimum against background)
- UI component states (disabled, selected, hovered) have sufficient contrast
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.
- 8d ago First seen · 261 lines · 31 tokens per session scan A 3fec6739a413
accessibility is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (28 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 2,375 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-30.
Other skills, from other repositories
accessibility-compliance-accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.
ss-review
Review UI code for design system compliance, accessibility, and best practices.
ada-plan-view-accessibility
Use when checking simplified ADA-derived plan-view bathroom accessibility constraints such as turning space, door clear width, toilet centerline, grab bars, and lavatory knee/toe clearance.
mqc-litigation-visual-redraw
Redraw a litigation diagram into a restrained, court-ready presentation graphic (SVG + PNG) WITHOUT changing any text or legal meaning. Use this whenever the user supplies a case timeline, a legal process flowchart, OR a party/relationship diagram and wants it cleaned up, beautified, redrawn, made professional…
patent-block-diagram
A workflow that turns a natural-language description into an editable `.pbd` patent block diagram, renders it in the diagram editor, checks the image, and exports a PNG.
form-accessibility
WCAG 2.2 AA compliance for forms, ARIA patterns, focus management, keyboard navigation, and screen reader support. Use when implementing accessible forms in any framework. The compliance foundation that ensures forms work for everyone.