lighthouse-bridge

lighthouse-bridge is a skill for Gemini CLI from Community-Access/accessibility-agents. It costs 41 tokens per session (1,335 once invoked), scanned A, original, MIT.

A read-only connector between Lighthouse CI accessibility reports and an accessibility audit workflow. Lighthouse is a tool that checks web pages, while CI runs those checks automatically during development.

In plain words
What is it for?
Use it to find Lighthouse CI settings, inspect audited URLs and thresholds, normalize report findings, track accessibility-score changes, and compare them with local scans.
Why use it?
It brings automated accessibility results into one place, highlights score regressions, and removes duplicate findings without changing code or issue trackers.

Skill for Gemini CLI

Written for Gemini CLI: installed under .gemini/. Also seen: mentions subagents.

Install

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.

agentmods
npx agentmods add skills/community-access/accessibility-agents/lighthouse-bridge
Any agent
npx skills add Community-Access/accessibility-agents --skill lighthouse-bridge
Clone the repo
git clone --depth 1 https://github.com/Community-Access/accessibility-agents

Made for: Gemini CLI.

Wrote 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.

agentmods badge for lighthouse-bridge

README.md
[![agentmods](https://agentmods.dev/badge/skills/community-access/accessibility-agents/lighthouse-bridge.svg)](https://agentmods.dev/skills/community-access/accessibility-agents/lighthouse-bridge)
Your own site
<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>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,335 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash 3f365b201804, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

.gemini/extensions/a11y-agents/skills/lighthouse-bridge/SKILL.md · 167 lines

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:

  1. Look for .github/workflows/*.yml files containing treosh/lighthouse-ci-action or lhci autorun
  2. Check for config files: lighthouserc.js, lighthouserc.json, .lighthouserc.js, .lighthouserc.json, .lighthouserc.yml
  3. If found, extract the configuration:
    • urls -- the list of URLs being audited
    • numberOfRuns -- how many times each URL is tested
    • assertions -- score budgets and thresholds (especially categories:accessibility)
    • uploadTarget -- where reports are stored
  4. 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):

  1. Extract the overall accessibility score (0-100)
  2. Extract individual audit results from the accessibility category
  3. 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"
  }
}

Read the full file on GitHub · 167 lines

Changes

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.

  1. 6d ago First seen · 167 lines · 41 tokens per session scan A 3f365b201804

Subscribe to this mod's changes

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.

Related

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.

PramodDutta/qaskills · 34 tokens

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…

ericrisco/rsc-harness · 86 tokens

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…

personamanagmentlayer/pcl · 98 tokens

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…

buiphucminhtam/forgewright · 73 tokens

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…

buiphucminhtam/forgewright · 61 tokens

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.

finsilabs/awesome-ecommerce-skills · 33 tokens