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.
git 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/p3-ux-a11y)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-ux-a11y"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-ux-a11y.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.1 | $0.00000 | $0.00954 |
| Opus 5 | $0.00000 | $0.00477 |
| Sonnet 5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
p3-ux-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 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-ux-a11y – Accessibility Concept
Defines WCAG target, contrast requirements, keyboard navigation, screen reader requirements and testing methods.
Argument: $ARGUMENTS = [WCAG level, e.g. "AA", "AAA"]
If provided: Use the level as the specification. If not provided: Recommend the appropriate level with justification.
Prerequisites
- UX_CONCEPT.md with wireframes and dark mode strategy
Agent
- Type: konzeptor
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From UX_CONCEPT.md: Wireframe elements (short list) and dark mode tokens
- Accessibility requirements (e.g. red-green color blindness)
- From FEATURES.md: Interactive elements (short list)
Prompt Template
Goal: Create accessibility concept. WCAG target: $ARGUMENTS
Context: [inline from UX_CONCEPT.md, CLAUDE.md]
Output Format:
- WCAG level with justification (1 sentence)
- Color contrasts: minimum ratios text (4.5:1), UI (3:1)
- Keyboard navigation: Table | Flow | Tab Order | Focus Indicator |
- Screen reader: Table | Element | ARIA Label | Role |
- Color blindness: concrete examples where non-color indicators are needed
- Testing methods: list of tools for phase 6
Constraints:
- ONLY accessibility, NO wireframes, NO dark mode (contrast reference only)
- Max. 5 flows for keyboard navigation
- Max. 10 ARIA elements
- Testing methods must name concrete tool names
Orchestrator Checkpoint
- WCAG level justified?
- Color blindness requirement considered?
Write Detail File
Write the result to docs/architecture/A11Y.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: ux-a11y
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## WCAG Target (with justification), ## Color Contrasts, ## Keyboard Navigation, ## Screen Reader, ## Color Blindness, ## Testing Methods.
(File replaces the legacy ACCESSIBILITY.md name — keep the new A11Y.md going forward.)
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 Changed 4fd921f96187
- 3d ago First seen · 92 lines · 0 tokens per session scan A bea6a4d2144c
p3-ux-a11y 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 954 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
e2e
Generate and run E2E tests with Playwright.
test-suite
Run comprehensive test suite with coverage analysis.
health-check
Perform a comprehensive, read-only end-to-end review of any portfolio app across three layers — Frontend (E2E), Database integrity, and Audit Log & User Activity — and produce a structured, observations-only report. Optionally, on explicit opt-in, generate (never apply) the infrastructure provisions needed so future…
gba-test
$ARGUMENTS: test mode — game profile defines available modes (e.g., smoke, gameplay, save, stress, full, ai, battle, nav, custom ).
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.