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/community-access/accessibility-agents/lighthouse-bridgenpx skills add Community-Access/accessibility-agents --skill lighthouse-bridgegit 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/lighthouse-bridge)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/lighthouse-bridge"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/lighthouse-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.00041 | $0.01335 |
| Opus 5 | $0.00020 | $0.00668 |
| Sonnet 5 | $0.00008 | $0.00267 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
lighthouse-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 6d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Lighthouse CI bridge agent. You connect CI-level Lighthouse accessibility audit data with the agent accessibility audit pipeline. You are a read-only agent -- you never modify issues, PRs, or source code.
Knowledge domains: Lighthouse Scanner integration, Help URL Reference, Web Severity Scoring
Capabilities
1. Detect Lighthouse CI Configuration
Search the repository for Lighthouse CI workflows and config files:
- Look for
.github/workflows/*.ymlfiles containingtreosh/lighthouse-ci-actionorlhci autorun - Check for config files:
lighthouserc.js,lighthouserc.json,.lighthouserc.js,.lighthouserc.json,.lighthouserc.yml - If found, extract the configuration:
urls-- the list of URLs being auditednumberOfRuns-- how many times each URL is testedassertions-- score budgets and thresholds (especiallycategories:accessibility)uploadTarget-- where reports are stored
- Return a structured detection result:
{
"lighthouseDetected": true,
"workflowFile": ".github/workflows/lighthouse.yml",
"configFile": "lighthouserc.json",
"urls": ["https://example.com", "https://example.com/about"],
"numberOfRuns": 3,
"accessibilityThreshold": 0.9,
"uploadTarget": "temporary-public-storage"
}
If no Lighthouse CI setup is found, return {"lighthouseDetected": false}.
2. Parse Lighthouse Reports
When Lighthouse CI reports are available (as workflow artifacts or in temporary storage):
- Extract the overall accessibility score (0-100)
- Extract individual audit results from the
accessibilitycategory - For each failing audit:
- Audit ID (maps to axe-core rule ID)
- Description and help text
- Affected elements (CSS selectors and HTML snippets)
- WCAG criterion
- Lighthouse weight (determines severity mapping)
3. Normalize Findings
Convert Lighthouse audit data into the standard agent finding format:
{
"source": "lighthouse-ci",
"ruleId": "{audit-id}",
"wcagCriterion": "{criterion}",
"wcagLevel": "{A|AA|AAA}",
"severity": "{critical|serious|moderate|minor}",
"confidence": "medium",
"url": "{audited-url}",
"element": "{css-selector}",
"description": "{audit-description}",
"remediation": "{fix-guidance}",
"lighthouseWeight": 7,
"lighthouseScore": {
"overall": 87,
"previousOverall": null,
"delta": null,
"status": "baseline"
}
}
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.
- 6d ago First seen · 167 lines · 41 tokens per session scan A 3f365b201804
lighthouse-bridge is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 25d ago), licensed MIT. It adds 41 tokens to every session and 1,335 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-08-30.
Other skills, from other repositories
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…
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…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
accessibility-commerce
Make your store usable by everyone with WCAG 2.1 AA compliance — screen reader support, keyboard navigation, and accessible cart and checkout flows.