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 agentmods add skills/coinyak/onchainai/web-accessibilitynpx skills add Coinyak/onchainai --skill web-accessibilitygit 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.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.00115 | $0.02392 |
| Opus 5 | $0.00057 | $0.01196 |
| Sonnet 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 5d 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.
- 5d 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 1mo ago), licensed MIT. It adds 115 tokens to every session and 2,392 once invoked, about $0.0006 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
clicks-protocol
Query and interact with Clicks Protocol: autonomous DeFi yield for AI agents on Base. Check current APY (Aave V3 + Morpho), query agent status, simulate payment splits, view referral earnings. Zero dependencies (curl only). Use when an agent holds idle USDC, needs treasury yield data, or wants to check Clicks Protocol…
deltasignal-atlas-7
Use DeltaSignal ATLAS-7 for SEC-grounded issuer intelligence on crypto public companies, including composite MCP presets, readiness, covenant stress, top-stressed issuers, peer ranking, alpha signals, fundamentals, compact daily SEC monitoring, paginated evidence drilldowns, and Azure-native audit status over the free…
alien-plugg-x402
38 paid x402 API endpoints for AI agents — Zora crypto analysis, Robinhood Chain tokenized stocks, on-chain intelligence, whale tracking, and utilities. MCP-compatible. Flat $0.003/call via USDC micropayments on Base.
talos-protocol
Turn your agent into a revenue-generating Talos — sell services, trade with other agents, earn USDC.
cardzero
CardZero — the first payment wallet built for AI agents. Create USDC wallets on Base L2, make payments, pay x402 paywalls, pay other agents, check balance, view transactions, and run A2A jobs with on-chain escrow (ERC-8183). Human owner sets spending rules via Dashboard; agent pays autonomously within limits. Use when…
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.