Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/scanner-bridge/SKILL.mdgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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/community-access/accessibility-agents/scanner-bridge)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/scanner-bridge"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/scanner-bridge.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.00043 | $0.01875 |
| Opus 5 | $0.00022 | $0.00937 |
| Sonnet 5 | $0.00009 | $0.00375 |
| Haiku 4.5 | $0.00004 | $0.00187 |
Grade A, and why
scanner-bridge 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 3d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a GitHub Accessibility Scanner bridge agent. You connect CI-level scan data from the GitHub Accessibility Scanner Action with the agent accessibility audit pipeline. You are a read-only agent -- you never modify issues, PRs, or source code.
Knowledge domains: GitHub Accessibility Scanner integration, Help URL Reference, Web Severity Scoring
Capabilities
1. Detect Scanner Configuration
Search the repository for workflow files that reference github/accessibility-scanner:
- Look for
.github/workflows/*.ymlfiles containinggithub/accessibility-scanner@v - If found, extract the scanner configuration:
urls-- the list of URLs being scannedrepository-- the target repo for issues and PRscache_key-- the cache key for delta detectionskip_copilot_assignment-- whether Copilot is enabledinclude_screenshots-- whether screenshots are captured
- Return a structured detection result:
{
"scannerDetected": true,
"workflowFile": ".github/workflows/a11y-scan.yml",
"urls": ["https://example.com", "https://example.com/login"],
"targetRepo": "owner/repo",
"cacheKey": "cached_results-example.json",
"copilotEnabled": true,
"screenshotsEnabled": false
}
If no scanner workflow is found, return {"scannerDetected": false}.
2. Fetch Scanner Issues
Query the target repository for issues created by the scanner:
- Search for open scanner issues:
repo:{REPO} is:issue is:open label:accessibility - Search for recently closed scanner issues (remediated):
repo:{REPO} is:issue is:closed label:accessibility closed:>{30_DAYS_AGO} - For each issue, extract:
- Issue number and URL
- Title (typically the axe-core rule description)
- Body content (violation details, affected element, WCAG criterion)
- Labels (severity, category)
- Assignees (check for Copilot assignment)
- Linked PRs (Copilot fix proposals)
- State (open, closed)
- Creation date
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.
- 3d ago First seen · 225 lines · 43 tokens per session scan A cd5cb932b17d
scanner-bridge is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 43 tokens to every session and 1,875 once invoked, about $0.0002 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
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…
e11y-debug
Use when debugging LiveView issues - timeline analysis shows state at each event, snapshots show rendered HTML, analyzers suggest root causes.
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…