Borrowing it
Nothing to install: this file belongs to Coinyak/onchainai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Coinyak/onchainai/main/.agents/skills/web-accessibility/SKILL.mdgit clone --depth 1 https://github.com/Coinyak/onchainaiWrote 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/coinyak/onchainai/web-accessibility)<a href="https://agentmods.dev/skills/coinyak/onchainai/web-accessibility"><img src="https://agentmods.dev/badge/skills/coinyak/onchainai/web-accessibility/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/coinyak/onchainai/web-accessibility"><img src="https://agentmods.dev/badge/skills/coinyak/onchainai/web-accessibility.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.00115 | $0.02392 |
| Opus 5.5 | $0.00046 | $0.00957 |
| Sonnet 5.5 | $0.00023 | $0.00478 |
| Haiku 4.5 | $0.00012 | $0.00239 |
Grade A, and why
web-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 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Accessibility
Use this skill when the job is to name the failing accessibility surface, fix it at the right layer, and leave behind a short remediation + verification packet.
The job is not to dump generic WCAG prose, paste raw scanner output, or absorb every neighboring frontend concern.
This skill should:
- classify the failing accessibility surface,
- separate automated findings from manual or assistive-technology follow-up,
- choose the smallest credible remediation packet,
- keep routed-app feedback and focus behavior explicit,
- route broader design/layout/component-governance work honestly.
Read these support docs first:
- references/intake-packets-and-route-outs.md
- references/audit-remediation-checklist.md
- references/handoff-boundaries.md
When to use this skill
- A team says “make this accessible” and the missing accessibility surface is still unclear
- axe, Lighthouse, Accessibility Insights, Pa11y, QA notes, or user reports need to be turned into one remediation plan instead of a raw finding dump
- You need to decide whether the main issue is semantics, keyboard/focus, labels/announcements, reflow/contrast/motion, media alternatives, or routed-app navigation feedback
- A modal, form, nav, menu, table, dashboard, or routed flow needs manual-vs-automated verification guidance before release
- Screen-reader, keyboard-only, or zoom/reflow issues are suspected, but ownership and next checks are unclear
When not to use this skill
- The main task is broad UI polish, heuristic review, hierarchy, or interface consistency →
web-design-guidelines - The main task is reusable primitive / slot / variant API design or component-family ownership →
ui-component-patterns - The main task is viewport adaptation, breakpoint strategy, container-query planning, or layout overflow control →
responsive-design - The main task is token governance, contribution rules, or system-wide frontend standards →
design-system - The task is only to run one tool and paste raw results; run the tool directly, then return here to prioritize remediation and manual follow-up
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 227 lines · 115 tokens per session scan A 5f764300ea97
web-accessibility is a skill published in the GitHub repository Coinyak/onchainai (1 stars, last pushed 3mo ago), licensed MIT. It adds 115 tokens to every session and 2,392 once invoked, about $0.0005 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 skills, from other repositories
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
kiranism-shadcn-dashboard
Guide for building features, pages, tables, forms, themes, and navigation in this Next.js 16 shadcn dashboard template. Use this skill whenever the user wants to add a new page, create a feature module, build a data table, add a form, configure navigation items, add a theme, set up RBAC access control, or work with…
sandbox
Visual HTML canvas sandbox for agent-driven UI and live previews.
omd-apply
A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.
common-architecture-diagramming
Draws architecture diagrams as editable draw.io files with a fixed house style, C4 levels, evidence-tagged shapes, and optional multi-view identity checks. Use when producing a system context, container, component, deployment, data flow, sequence, state, or ERD, or redrawing an ASCII or Mermaid one.
system-design-diagramming
Draw system diagrams in the Archify visual language: a typed JSON spec rendered as dark-canvas SVG with numbered lanes, semantic node colors, masked edge labels, and a legend. Covers architecture, workflow, sequence, dataflow, and lifecycle views. Use for any design-session diagram.