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 MonumentalSystems/Atlas-Agent-Teams --skill accessibilitygit clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-TeamsWrote 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/monumentalsystems/atlas-agent-teams/accessibility)<a href="https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/accessibility"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/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/monumentalsystems/atlas-agent-teams/accessibility"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/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.00028 | $0.02283 |
| Opus 5 | $0.00014 | $0.01141 |
| Sonnet 5 | $0.00006 | $0.00457 |
| Haiku 4.5 | $0.00003 | $0.00228 |
Grade A, and why
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 9d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility
WCAG 2.1 Guidelines and Compliance Levels
WCAG Principles (POUR)
- Perceivable: Information and UI components must be presentable in ways users can perceive
- Operable: UI components and navigation must be operable
- Understandable: Information and operation of UI must be understandable
- Robust: Content must be robust enough to be interpreted by assistive technologies
Compliance Levels
- Level A: Minimum level of accessibility
- Level AA: Standard level, required by many laws and regulations
- Level AAA: Highest level, rarely required but ideal
WCAG 2.1 Success Criteria
- 1.1 Text Alternatives: Provide text alternatives for non-text content
- 1.2 Time-Based Media: Provide alternatives for time-based media
- 1.3 Adaptable: Create content that can be presented in different ways
- 1.4 Distinguishable: Make it easier to see and hear content
- 2.1 Keyboard Accessible: Make all functionality available from a keyboard
- 2.2 Enough Time: Provide users enough time to read and use content
- 2.3 Seizures and Physical Reactions: Do not design content that causes seizures
- 2.4 Navigable: Provide ways to help users navigate and find content
- 2.5 Input Modalities: Make it easier to use inputs other than keyboard
- 3.1 Readable: Make text content readable and understandable
- 3.2 Predictable: Make Web pages appear and operate in predictable ways
- 3.3 Input Assistance: Help users avoid and correct mistakes
- 4.1 Compatible: Maximize compatibility with current and future user agents
Screen Reader Compatibility
Screen Reader Basics
- Popular Screen Readers: NVDA (Windows), JAWS (Windows), VoiceOver (Mac/iOS), TalkBack (Android)
- Testing: Test with multiple screen readers for comprehensive coverage
- Semantic HTML: Use proper HTML elements for screen reader compatibility
- ARIA Attributes: Use ARIA when HTML alone is insufficient
- Focus Management: Ensure logical focus order for keyboard and screen reader users
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.
- 9d ago First seen · 213 lines · 28 tokens per session scan A 80c730eb6b3d
accessibility is a skill published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 28d ago), licensed MIT. It adds 28 tokens to every session and 2,283 once invoked, about $0.0001 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-30.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…