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/jeet129/praxis/accessibilitynpx skills add jeet129/praxis --skill accessibilitygit clone --depth 1 https://github.com/jeet129/praxisWrote 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/jeet129/praxis/accessibility)<a href="https://agentmods.dev/skills/jeet129/praxis/accessibility"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/accessibility.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.00108 | $0.02941 |
| Opus 5 | $0.00054 | $0.01470 |
| Sonnet 5 | $0.00022 | $0.00588 |
| Haiku 4.5 | $0.00011 | $0.00294 |
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 5d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility
capability: quality-and-security
domain: frontend
state: active
dependencies:
- engineering-standards
- design-system
- nfr-definition
triggers:
- "designing new screens or components"
- "implementing new UI components"
- "auditing existing UI for a11y compliance"
- "setting up axe in CI"
- "establishing WCAG conformance target"
- "reviewing a PR that touches UI"
outputs:
- a11y checklist per component/flow
- axe rules configuration + CI integration
- severity-tagged a11y findings (during review/audit)
- manual testing protocol for keyboard / screen reader
- WCAG conformance attestation (per release)
consumers:
- ux-designer (applies at design time)
- frontend-developer (applies at code time)
- code-review (a11y aspect of reviews)
- qa-engineer (manual a11y testing)
- compliance-privacy (feeds into regulatory attestation)
references: []
Accessibility is not a checklist to satisfy regulation; it's a discipline that makes the product work for everyone, including the team's own users when they're tired, on a low-bandwidth connection, using one hand, or relying on a screen reader. Built in from the start; nearly free. Retrofitted later; expensive.
This skill spans design and code. The UX Designer applies it during wireframing (color contrast, semantic structure, focus order). The Frontend Developer applies it during implementation (ARIA, keyboard interaction, focus management). The Code Reviewer audits it during review. QA runs manual checks before release.
When this skill fires
- A new screen or component is being designed — UX Designer applies the design-time checks.
- A new component is being implemented — FE Dev applies the code-time checks.
- A PR touches UI — Code Reviewer runs the a11y dimension of
code-review. - A release is being prepared — QA runs the manual testing protocol.
- An a11y audit is being scheduled — auditor uses the full checklist.
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.
- 5d ago First seen · 240 lines · 108 tokens per session scan A 5fbfc4d8d665
accessibility is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed today), licensed MIT. It adds 108 tokens to every session and 2,941 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…