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 almasumdev/awesome-mobile-accessibility-agent-skills --skill dark-mode-a11ygit clone --depth 1 https://github.com/almasumdev/awesome-mobile-accessibility-agent-skillsWrote 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/almasumdev/awesome-mobile-accessibility-agent-skills/dark-mode-a11y)<a href="https://agentmods.dev/skills/almasumdev/awesome-mobile-accessibility-agent-skills/dark-mode-a11y"><img src="https://agentmods.dev/badge/skills/almasumdev/awesome-mobile-accessibility-agent-skills/dark-mode-a11y/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/almasumdev/awesome-mobile-accessibility-agent-skills/dark-mode-a11y"><img src="https://agentmods.dev/badge/skills/almasumdev/awesome-mobile-accessibility-agent-skills/dark-mode-a11y.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.00037 | $0.01157 |
| Opus 5 | $0.00018 | $0.00579 |
| Sonnet 5 | $0.00007 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
dark-mode-a11y 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 10d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 10d ago First seen · 121 lines · 37 tokens per session scan A 931258f2c3d4
dark-mode-a11y is a skill published in the GitHub repository almasumdev/awesome-mobile-accessibility-agent-skills (1 stars, last pushed 4mo ago), with no licence file. It adds 37 tokens to every session and 1,157 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-09-01.
Other skills, from other repositories
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
a11y-toolkit
Use for ALL accessibility work — WCAG 2.2 audits of URLs or HTML, real rendered contrast checks (including text over images, pixel-level), color-pair contrast and nearest passing color, European Accessibility Act / RD 1112/2018 accessibility statements, pre-deploy regression detection (accessible names, tab order)…
Modern Web Accessibility for Interactive UI
An accessibility review for interactive interface elements such as dialogs, menus, popovers, tabs, forms, and live updates.
implement-component
Implements production-ready UI using DB UX Design System v3 components, tokens, and icons with a discovery-first approach.
wcag-accessibility
Use when building UI components, reviewing color contrast, adding ARIA attributes, handling keyboard navigation, writing alt text, creating forms, or ensuring WCAG 2.2 AA compliance. Covers color contrast ratios, semantic HTML, focus management, screen reader support, motion preferences, and accessibility auditing.
Accessibility Checklist
A concrete, checklist-driven pass for semantic HTML, ARIA, keyboard navigation, contrast, alt text, and focus management.