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/arnosdeus/agent-toolkit/accessibility-reviewnpx skills add Arnosdeus/agent-toolkit --skill accessibility-reviewgit clone --depth 1 https://github.com/Arnosdeus/agent-toolkitWrote 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/arnosdeus/agent-toolkit/accessibility-review)<a href="https://agentmods.dev/skills/arnosdeus/agent-toolkit/accessibility-review"><img src="https://agentmods.dev/badge/skills/arnosdeus/agent-toolkit/accessibility-review.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 | $0.00034 | $0.00188 |
| Opus 5 | $0.00017 | $0.00094 |
| Sonnet 5 | $0.00007 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
accessibility-review 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 3d 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 Review
Procedure and output
Test keyboard paths, focus order, accessible names, and important states before
reviewing markup. Report BLOCKER, MAJOR, MINOR, or NOTE findings with
file:line — user impact — evidence — fix; distinguish automated results from
manual screen-reader verification.
Check keyboard navigation, focus visibility and management, semantic HTML, labels, field errors, ARIA correctness, contrast, accessible names, screen-reader behavior, reduced motion, target sizes, dialogs, tables, and navigation. Prefer native semantics over ARIA. Use Playwright and the accessibility tree where practical, and distinguish observed issues from items requiring assistive-tech or manual verification.
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.
- 3d ago First seen · 21 lines · 34 tokens per session scan A bbebc445236c
accessibility-review is a skill published in the GitHub repository Arnosdeus/agent-toolkit (2 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 188 once invoked, about $0.0002 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
frontend-design
Designs, builds, or refactors user-facing web or application interfaces with deliberate visual direction, typography, color and spacing tokens, content hierarchy, responsive behavior, accessible interaction states, and real rendered-surface verification. Use for pages, components, dashboards, landing pages, design…
design
Use for UI, UX, visual hierarchy, frontend-design judgment, references, redesigns, and design critique when the user's Emulo taste should guide the task. Do not use for unrelated execution or marketing/social writing alone.
frontend-ui-audit
Frontend UI consistency audit for React + Tailwind codebases. Use when reviewing component refactors, UI cleanup batches, or answering "should this use the design system?" — checks design-system adoption, arbitrary Tailwind values vs tokens, hardcoded sizes and colors, accessibility basics, and repeated visual…
design-system
Dotbot CRT/retro-futuristic design system: tokens, components, patterns, and anti-patterns for the control panel UI.
using-design-system
Ensures consistent use of X-components design system instead of Material3 when working on feature UI code. Automatically activates for Composable functions in feature modules or when user mentions UI/screens/components.
factory-design
Design-system discipline distilled across builds. Semantic token vocabulary (name intent, not palette position), CSS variables bridged into Tailwind, dark/light as a variable swap, single- vs two-layer token systems, component primitives as token consumers, when to promote a repeated utility cluster into a primitive…