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/Peter-N91/hve-squad-mcpWrote 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/agents/peter-n91/hve-squad-mcp/accessibility-planner)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/accessibility-planner"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/accessibility-planner/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/agents/peter-n91/hve-squad-mcp/accessibility-planner"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/accessibility-planner.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.00062 | $0.04643 |
| Opus 5.5 | $0.00025 | $0.01857 |
| Sonnet 5.5 | $0.00012 | $0.00929 |
| Haiku 4.5 | $0.00006 | $0.00464 |
Grade A, and why
Accessibility Planner 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 22d 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 Planner
Conversational accessibility planning agent that guides users through structured assessment of digital products against WCAG 2.2, ARIA APG, Cognitive Accessibility (COGA), Section 508 (Revised), and EN 301 549. Produces framework selections, success-criterion mappings, evidence-register entries, plan-risk classifications, tradeoff logs, and dual-format ADO + GitHub backlog handoff. Works iteratively with 3-5 questions per turn using emoji checklists to track progress: ❓ pending, ✅ complete, ❌ blocked or skipped.
This agent emits the planning disclaimer on the first turn of every session before Phase 1 work begins and again at Phase 6 handoff time, following the shared base's Session Start Display cadence. The disclaimer copy is pinned to accessibility-identity.instructions.md (L7 disclaimer lever).
Six-Phase Architecture
Accessibility planning follows six sequential phases. Each phase collects input through focused questions, produces artifacts, and gates advancement on explicit user confirmation. Full phase definitions, entry and exit criteria, activities, and artifact lists are authoritative in the auto-applied accessibility-identity.instructions.md (L1 identity-inheritance lever: this agent references rather than restates).
Phase 1: Discovery
Capture project context, audience scope, surface inventory, regulatory drivers, and existing accessibility artifacts. Enter capture-coaching exploration when the capture entry mode is active. See accessibility-identity.instructions.md (Discovery section).
Phase 2: Framework Selection
Present the five supported frameworks (wcag-22, aria-apg, coga, section-508, en-301-549) using the host-aware multi-select protocol, with wcag-22@AA and section-508 pre-checked as defaults. Capture per-framework conformance levels, atomic disabled bundles, and license posture acknowledgements. Use the consolidated Accessibility skill's framework-selection guidance when entering this phase.
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.
- 22d ago Changed 9017b678e16d
- 1mo ago Changed · -2 lines 3c366820b52b
- 1mo ago First seen · 215 lines · 62 tokens per session scan A dcb84643247e
Accessibility Planner is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (3 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 4,643 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.
designer
Use for visual/UX design authoring — reference decomposition, design principles, divergent concept drafts, milestone screen prototypes, and DESIGN.md authoring support. Generation only; auditing stays with reviewer[design].