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/vmobifystudio/app-dev-team/accessibility-gatenpx skills add vmobifystudio/app-dev-team --skill accessibility-gategit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/accessibility-gate)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/accessibility-gate"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/accessibility-gate.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.00074 | $0.00636 |
| Opus 5 | $0.00037 | $0.00318 |
| Sonnet 5 | $0.00015 | $0.00127 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
accessibility-gate 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility gate
The studio's position, from the plan: accessibility does not need a specialist role, it needs a gate that can fail. This is that gate. It runs on the diff, not on the finished app, because a retrofit is an order of magnitude more expensive than doing it in the ticket.
Where a platform auditor exists, spawn it first and fold its findings in — axiom:accessibility-auditor
on iOS, ui-design:accessibility-audit elsewhere. Both are external and optional (separate
plugins, not this one's skills/). Missing → record N/A: <tool> — not installed, walk the list by
hand, never file the absence as a defect.
The gate
Each item is PASS or FAIL: <what and where>. There is no partial credit and no "minor".
- Every interactive element has an accessible label that says what it does — not its icon name. An unlabelled icon button is a control that does not exist for a screen-reader user.
- Reading order matches visual order, and grouped content is grouped for the screen reader too.
- Every state change is announced — loading finished, error appeared, item deleted. A silent state change strands the user in the previous screen.
- Touch targets are at least 44pt (iOS) / 48dp (Android), including in dense lists.
- Contrast: 4.5:1 body text, 3:1 large text and non-text indicators. Checked against the token, in both light and dark.
- Colour is never the only signal. Error, selection and status carry a shape, an icon or text.
- Dynamic Type / font scaling to the largest supported size does not clip, truncate meaning, or overlap. Test at the maximum, not at 120%.
- Keyboard and switch access reach every action, focus is always visible, and focus is never
trapped. On web this includes a skip link and a visible
:focus-visiblestyle. - Reduce-motion is honoured and still gives the user feedback (
interaction-motion). - Media has an alternative — alt text, caption, or transcript.
Verdict
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 · 46 lines · 74 tokens per session scan A d34ae3a93cd1
accessibility-gate is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 24d ago), licensed MIT. It adds 74 tokens to every session and 636 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
fidelity-gate
Build a UI against a frozen visual reference without drift - an inventory extracted before any code, a relics list, and a gate that MEASURES computed styles on a fixture carrying the reference's own data. Use when a mockup, design spec or screenshot is the contract.
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
execute-task
Implement one task (or a cohesion bundle) from a signed-off spec (Ready or Active): recompute the execution freshness gate, write the verifying test first, implement to green, run the project's full CI with adaptive retry, converge via the configured reviewsequence (default /polish --nested), then open a draft PR…
builder
Detect a project's stack and recommend or apply the universal mechanical quality guards from planwright's core catalog (formatter, linters, type-checker, test runner, secret scan, commit hooks, CI gate), plus the growable breadth dimensions. Escalates stake-bearing decisions (auth, data modeling, security posture…
spec-walkthrough
Render a spec bundle (or a chosen slice) into a plain-language, didactic comprehension artifact a human reads and judges for themselves: an unaided cold read before kickoff, re-orientation mid-execution, or onboarding to a finished or abandoned spec. Standalone and strictly read-only: it renders any status, never…
drain
Run the on-demand drain pass over every spec bundle's Gate deferral entries: evaluate structured GATE(when:) conditions, surface date and free-text gates, report malformed ones, inventory each live bundle's [manual] test-spec entries, and surface the observations log's unmined state. Read-only; nothing is…