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/xonovex/platform/accessibility-guidenpx skills add xonovex/platform --skill accessibility-guidegit clone --depth 1 https://github.com/xonovex/platformWhat 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 | $0.00088 | $0.00766 |
| Opus 5 | $0.00044 | $0.00383 |
| Sonnet 5 | $0.00018 | $0.00153 |
| Haiku 4.5 | $0.00009 | $0.00077 |
Grade A, and why
accessibility-guide 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 2d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Assurance
Make accessibility a versioned, testable quality and governance concern without requiring one platform, scanner, or conformance claim.
Essentials
- Pin the target: record the standard, version, level, applicable criteria, exact subject revision, environments, and user journeys, see references/assessment-and-evidence.md
- Design with affected users: include perceivable, operable, understandable, and robust outcomes from discovery through content and interaction design, see references/design-and-implementation.md
- Layer the evidence: combine deterministic inspection, automated checks, keyboard and zoom testing, representative assistive technology, and qualified human review, see references/assessment-and-evidence.md
- Publish criterion outcomes: report pass, fail, not-applicable, and not-tested with origins, limitations, findings, gaps, freshness, and native references, see references/assessment-and-evidence.md
- Govern exceptions and drift: scope, own, expire, review, remediate, reassess, and retire accessibility decisions, see references/governance-and-operations.md
- Keep tools in their lane: platform skills own implementation APIs; scanners and agents provide evidence but never accountable conformance by themselves
Gotchas
- An automated scanner covers only what it can observe; a clean report is not proof that every applicable criterion passes.
not-applicableneeds a criterion-specific reason and reviewer; it is not a synonym for untested or inconvenient.- Conformance applies to the declared subject, scope, version, level, and dependencies. A changed UI, content path, component, platform, or assistive-technology environment may invalidate evidence.
- An exception preserves a known gap and remediation duty. It never changes a failed criterion into a pass or establishes conformance.
- Crosswalks between accessibility standards, laws, and design guidance are contextual; they do not establish equivalence, certification, or legal compliance.
What ships with it
6 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.
- 2d ago First seen · 42 lines · 88 tokens per session scan A 17387b51e3cb
accessibility-guide is a skill published in the GitHub repository xonovex/platform (5 stars, last pushed 2d ago), licensed MIT. It adds 88 tokens to every session and 766 once invoked, about $0.0004 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
debugging-output-and-previewing-html-using-ray
Use when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop application.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
project-snmp-profiles-authoring
Use when editing Netdata SNMP profile YAMLs, topology SNMP profiles, ddsnmp profile parsing, or profile-format documentation. Requires checking source MIB field accessibility, especially MAX-ACCESS not-accessible INDEX objects, before adding or changing profile symbols.
fix-issues
Fix a batch of open GitHub issues end to end - one git worktree and one agent per issue (feature-dev for implementation, review-pr for review), individual PRs into develop, a release PR to main with a final multi-agent integration review, and optional tag/release/issue-comment publishing. Use when the user asks to…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
kurtosis-ethereum
Run Ethereum multi-client devnets using Kurtosis and the ethpandaops/ethereum-package. Use for spinning up local devnets, syncing public testnets, validating cross-client interop, testing fork transitions, shadowforks, running assertoor checks, debugging CL/EL client interactions, or verifying new feature…