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 commands/jonase47/ccpr/p6-a11y-screenreadergit clone --depth 1 https://github.com/jonase47/ccprWrote 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/commands/jonase47/ccpr/p6-a11y-screenreader)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-a11y-screenreader"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-a11y-screenreader.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.00000 | $0.00904 |
| Opus 5 | $0.00000 | $0.00452 |
| Sonnet 5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
p6-a11y-screenreader 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 today.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-a11y-screenreader – ARIA, Semantics & Alt Texts
Checks screen reader compatibility: semantic HTML, ARIA attributes, alt texts, live regions.
Argument: $ARGUMENTS = [page/component]
If provided: Check the specified page/component. If not provided: Check all screens.
Prerequisites
- UI implemented
Agent
- Type: ux-designer
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads in advance and delivers inline:
- From src/: HTML structure (semantics, ARIA attributes, images, forms)
- From ACCESSIBILITY.md: Screen reader requirements
Prompt Template
Goal: Check screen reader compatibility for: [page/component]
HTML Structure: [inline from src/]
Output Format: Checklist:
# Check Point Status Finding 1 Images have alt texts (or aria-hidden) OK/FINDING ... 2 Form inputs have labels OK/FINDING ... 3 Interactive elements: role/aria-label OK/FINDING ... 4 Status changes via aria-live OK/FINDING ... 5 Icons without text have aria-label OK/FINDING ... 6 Semantic HTML (header, nav, main) OK/FINDING ... 7 Heading hierarchy correct OK/FINDING ... Constraints:
- Screen reader compatibility ONLY – no colours, no keyboard
- Focus on semantic correctness and ARIA completeness
Orchestrator Checkpoint
- All images, forms, buttons checked?
- aria-live present for dynamic content?
Write Detail File
Write the result to docs/quality/a11y_screenreader.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P6
subskill: a11y-screenreader
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Scope, ## Findings (ARIA + semantics checklist), ## Severity Summary.
Update Sub-Index
Update docs/quality/A11Y.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[a11y_screenreader.md](a11y_screenreader.md)with statuscomplete(orneeds-rework). - Lift any blocking screen-reader finding into Open Risks of the sub-index.
- Do not edit
QA.mddirectly.
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.
- today First seen · 91 lines · 0 tokens per session scan A 3a9f76e45d61
p6-a11y-screenreader is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 904 tokens. 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-03.
Other commands, from other repositories
design-intent
Guided UI/visual development with structured exploration, architecture design, and quality review.
prototype
Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery.
design
Early-stage design exploration — settle the shape of a feature/recipe/system before scoping its implementation. Re-entrant; agent-judged writes.
devteam-design
Command: /devteam:design [target] [options].
devteam-design-drift
Command: /devteam:design-drift [scope] [options].
flutter-review
Review Flutter/Dart code for idiomatic patterns, widget best practices, state management, performance, accessibility, and security. Invokes the flutter-reviewer agent.