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 bromso/metapowers --skill a11ygit clone --depth 1 https://github.com/bromso/metapowersWrote 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/bromso/metapowers/a11y)<a href="https://agentmods.dev/skills/bromso/metapowers/a11y"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/a11y.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.00009 | $0.00369 |
| Opus 5 | $0.00005 | $0.00185 |
| Sonnet 5 | $0.00002 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
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 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.
What it actually says
Accessibility Coaching
Review "$ARGUMENTS" through the lens of an accessibility specialist. Provide mentorship feedback on inclusive design, WCAG compliance, and assistive technology compatibility.
Prerequisites
None — this is a utility skill that can run anytime.
Process
-
Read the target:
- Read the file, component, or content specified in "$ARGUMENTS"
-
Check for project accessibility context:
- Look for
.metapowers/accessibility/directories for prior audit results - If the accessibility plugin's shared resources exist, read
plugins/accessibility/shared/wcag-21-aa-criteria.md
- Look for
-
Read reference material:
- Read
plugins/coaching/shared/feedback-format.mdfor output structure
- Read
-
Evaluate for accessibility:
- Perceivable: Alt text, captions, contrast, text resize, content reflow
- Operable: Keyboard access, focus management, no traps, timing, navigation
- Understandable: Language, predictability, input assistance, error messages
- Robust: Valid markup, ARIA usage, name/role/value, status messages
- Inclusive design: Does it work for users with visual, auditory, motor, and cognitive disabilities?
- Assistive technology: Will it work with screen readers, switch devices, voice control?
-
Write the coaching report to
.metapowers/coaching/$ARGUMENTS/a11y-review.mdfollowing the feedback format.
Output
The accessibility coaching report written to .metapowers/coaching/$ARGUMENTS/a11y-review.md. Present the score and top 3 suggestions to the user.
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 · 38 lines · 9 tokens per session scan A b8feecd766aa
a11y is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 369 once invoked, about $0.0000 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
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
design-web
Use when building or revising a marketing/landing/campaign page, register brand locked at Gate 0 — use design-webapp for app screens instead.
design-motion
Use when adding or reviewing motion on an already-settled layout or component — never to hide or compensate for an unfinished one.
design-review
Use when a design deliverable is about to be reported done — the final quality gate after design-motion or a mobile mockup.
design-ios
Use when designing an iOS or macOS screen or flow — deliverable is a device/window-framed HTML mockup and handoff spec, never SwiftUI code.