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 shahidshabbir-se/my-pi-setup --skill accessibility-a11ygit clone --depth 1 https://github.com/shahidshabbir-se/my-pi-setupWrote 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/shahidshabbir-se/my-pi-setup/accessibility-a11y)<a href="https://agentmods.dev/skills/shahidshabbir-se/my-pi-setup/accessibility-a11y"><img src="https://agentmods.dev/badge/skills/shahidshabbir-se/my-pi-setup/accessibility-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/shahidshabbir-se/my-pi-setup/accessibility-a11y"><img src="https://agentmods.dev/badge/skills/shahidshabbir-se/my-pi-setup/accessibility-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.00028 | $0.01064 |
| Opus 5 | $0.00014 | $0.00532 |
| Sonnet 5 | $0.00006 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
accessibility-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 11d 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.
This is a copy
100% identical to accessibility-a11y — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility (a11y) Best Practices
You are an expert in web accessibility and inclusive design. Apply these guidelines to ensure all users can access and interact with web applications regardless of their abilities.
Core Accessibility Principles
- Follow WCAG (Web Content Accessibility Guidelines) standards
- Use semantic HTML to improve accessibility and screen reader compatibility
- Ensure high accessibility standards using ARIA roles and native accessibility props
- Design for all users including those with visual, auditory, motor, and cognitive disabilities
- Test with various assistive technologies
Semantic HTML
Structural Elements
- Use semantic elements like
<header>,<main>,<footer>,<nav>,<article>,<section>,<aside> - Employ
<button>for interactive elements, not<div>or<span> - Use proper heading hierarchy (h1-h6) without skipping levels
- Use landmarks (e.g.,
<nav>,<main>,<aside>) for screen reader navigation - Avoid deprecated markup
Form Accessibility
- Associate labels with form inputs using
forandidattributes - Group related form elements with
<fieldset>and<legend> - Provide clear error messages and validation feedback
- Use appropriate input types (email, tel, number, etc.)
- Include placeholder text as supplementary hints, not replacements for labels
ARIA Implementation
When to Use ARIA
- Use ARIA roles and attributes to enhance accessibility where semantic HTML is insufficient
- Prefer native HTML elements over ARIA when possible
- Use
aria-labelfor elements without visible text labels - Implement
aria-describedbyfor additional context - Use
aria-liveregions for dynamic content updates
Common ARIA Patterns
- Use
role="button"only when a non-button element must act as a button - Implement
aria-expandedfor collapsible content - Use
aria-hidden="true"for decorative elements - Apply
aria-current="page"for navigation highlighting - Use
aria-labelledbyto reference visible labels
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.
- 11d ago First seen · 132 lines · 28 tokens per session scan A 790f2e77ff37
accessibility-a11y is a skill published in the GitHub repository shahidshabbir-se/my-pi-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 1,064 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to accessibility-a11y, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
flutter-development
Cross-platform development with Flutter and Dart for iOS, Android, Web, Desktop, and embedded. Use when building Flutter apps, implementing Material/Cupertino design, or optimizing Dart code.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.
generic-react-feature-developer
Guide feature development for React applications with architecture focus. Covers Zustand/Redux patterns, IndexedDB usage, component systems, lazy loading strategies, and seamless integration. Use when adding new features, refactoring existing code, or planning major changes.