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 a11y-auditgit 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-audit)<a href="https://agentmods.dev/skills/bromso/metapowers/a11y-audit"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/a11y-audit/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/skills/bromso/metapowers/a11y-audit"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/a11y-audit.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.00092 | $0.00488 |
| Opus 5.5 | $0.00037 | $0.00195 |
| Sonnet 5.5 | $0.00018 | $0.00098 |
| Haiku 4.5 | $0.00009 | $0.00049 |
Grade A, and why
a11y-audit 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 today.
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 Audit
Run a full WCAG accessibility audit on a Figma component or frame, covering design lint, contrast, color blindness, and focus order.
See also /accessibility:scope for the full audit path — target, WCAG level and test plan — rather than a one-pass Figma check.
Process
-
Identify the target. The user should provide a component name, node ID, or indicate the current selection.
-
Run all accessibility checks:
- Call
figma_a11y_lintwith the target node ID to check text size, touch targets, and image alt text - Call
figma_a11y_scorecardwith the target node ID for an overall scorecard - Call
figma_a11y_focus_orderwith the target node ID to validate tab order
- Call
-
Check color contrast. For each foreground/background pair found:
- Call
figma_a11y_contrast_checkwith the color values and size "normal" - Call
figma_a11y_contrast_checkwith size "large" for large text
- Call
-
Simulate color blindness. For the primary color pairs:
- Call
figma_a11y_color_blind_simfor protanopia, deuteranopia, and tritanopia - Note any pairs that lose sufficient contrast under simulation
- Call
-
Compile the audit report:
- Summary: total checks run, pass/fail counts
- Lint issues (text too small, touch targets, missing alt text)
- Contrast results (AA/AAA pass/fail per pair)
- Color blindness results
- Focus order analysis
- Remediation recommendations
-
Present the report to the user.
Output
A comprehensive accessibility audit report presented to the user with actionable remediation steps.
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.
- today First seen · 42 lines · 92 tokens per session scan A 7fc13dcdf9d7
a11y-audit is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 488 once invoked, about $0.0004 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-10-21.
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.
motion-art-direction
Use when a film needs a look before any scene code — ads, launch teasers, brand films, type-led films with no screenshots, or whenever a draft looks flat (white ground, small tiles, centered text, fades, slow camera drift, logo opener). Locks .motion/look.md at Gate 0 (3 text sketches → challenger locks the tone blind…
motion-craft
Use when deciding how a film beat looks and moves — motion density (a gesture in progress at every moment: 0.75 s gesture-free max, CTA still ≤ 1.2 s, beats every 0.5-1 s, ≥ 1 onset/s) with read time ≥ 0.25 s/word, one primary gesture with subordinate details, the two film types (cut-based edit, one continuous…
challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).