lighthouse-bridge

lighthouse-bridge is an agent for Claude Code from Community-Access/accessibility-agents. It costs 41 tokens per session (1,498 once invoked), scanned A, original, MIT.

A read-only bridge between Lighthouse CI accessibility reports and an accessibility review system. Lighthouse is a tool that audits web pages, while CI runs those checks automatically during development.

In plain words
What is it for?
Use it to detect Lighthouse CI setup, read audited URLs and thresholds, normalize accessibility results, and connect them to an audit pipeline.
Why use it?
It turns Lighthouse findings into a consistent format, tracks accessibility score changes, and removes duplicate findings from local scans.

Agent for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions subagents; Copilot chat-mode frontmatter (tools: vscode/*).

Good fit Use it to detect Lighthouse CI setup, read audited URLs and thresholds…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/community-access/accessibility-agents/lighthouse-bridge
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.

Clone the repo
git clone --depth 1 https://github.com/Community-Access/accessibility-agents

Made for: Claude Code.

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/agents/community-access/accessibility-agents/lighthouse-bridge.svg)](https://agentmods.dev/agents/community-access/accessibility-agents/lighthouse-bridge)
Your own site
<a href="https://agentmods.dev/agents/community-access/accessibility-agents/lighthouse-bridge"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/lighthouse-bridge.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,498 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.01498
Opus 5 $0.00020 $0.00749
Sonnet 5 $0.00008 $0.00300
Haiku 4.5 $0.00004 $0.00150

Measured 3d ago against content hash 72797539d8a2, 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 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.

.github/agents/lighthouse-bridge.agent.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Authoritative Sources

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.

Skills: lighthouse-scanner, 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)

Read the full file on GitHub · 180 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. 3d ago First seen · 180 lines · 41 tokens per session scan A 72797539d8a2

Subscribe to this mod's changes

lighthouse-bridge is an agent published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 41 tokens to every session and 1,498 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.

Related

Other agents, from other repositories

bench-runner

Executes a11y skill benchmarks across hosted and local model families. Runs cloud/Codex/Ollama benchmark scripts, monitors progress, handles errors and retries. Reports raw results to the team.

zivtech/accessibility-skills · 44 tokens

bench-reviewer

Reviews eval suite quality — fixture/rubric consistency, scoring accuracy, false positive traps, difficulty calibration. Read-only reviewer that identifies issues without fixing them.

zivtech/accessibility-skills · 35 tokens

fixture-builder

Creates and enriches eval suite fixtures — .md component files, .metadata.yaml grading criteria, and .rubric.yaml scoring definitions. Handles all three suites (critic, planner, perspective).

zivtech/accessibility-skills · 41 tokens

prism

Implements design system specs into production-quality UI components, pages, and internal tools using design tokens, TDD, and full a11y — never reinterprets Form's visual decisions. Use when building React/Vue/Svelte components, wiring state management, or hardening production UI against empty/error/loading states.…

jeremylongshore/tons-of-skills-marketplace · 78 tokens

a11y-planner

Accessibility Design Planner — 9-phase protocol for designing accessible implementations before coding. Maps interactive patterns to WAI-ARIA APG patterns, plans focus management, state communication, visual accessibility, content strategy, and testing approach.

zivtech/accessibility-skills · 50 tokens

a11y-role-auditor

ARRM-based accessibility role auditor — reviews artifacts from responsibility-based team role perspectives (visual design, UX design, front-end dev, content authoring, business analysis, testing) to produce role-attributed findings.

zivtech/accessibility-skills · 50 tokens