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 skills add itsnex1s/awesome-claude-skills --skill lighthouse-auditgit clone --depth 1 https://github.com/itsnex1s/awesome-claude-skillsWrote 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/itsnex1s/awesome-claude-skills/lighthouse-audit)<a href="https://agentmods.dev/skills/itsnex1s/awesome-claude-skills/lighthouse-audit"><img src="https://agentmods.dev/badge/skills/itsnex1s/awesome-claude-skills/lighthouse-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/itsnex1s/awesome-claude-skills/lighthouse-audit"><img src="https://agentmods.dev/badge/skills/itsnex1s/awesome-claude-skills/lighthouse-audit.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.01394 |
| Opus 5 | $0.00013 | $0.00697 |
| Sonnet 5 | $0.00005 | $0.00279 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
lighthouse-audit 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 12d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lighthouse-audit
Run Lighthouse performance audits on deployed websites. Checks Performance, Accessibility, Best Practices, and SEO scores.
Installation
# Lighthouse CLI (optional, for local audits)
npm install -g lighthouse
# agent-browser for visual testing
npm install -g agent-browser
agent-browser install
Quick Audit (CLI)
# Run Lighthouse audit
npx lighthouse https://example.com --output=json --output-path=/tmp/report.json
# Extract scores
cat /tmp/report.json | jq '{
performance: (.categories.performance.score * 100 | round),
accessibility: (.categories.accessibility.score * 100 | round),
bestPractices: (.categories["best-practices"].score * 100 | round),
seo: (.categories.seo.score * 100 | round)
}'
Detailed Audit
# Full audit with all categories
npx lighthouse https://example.com \
--output=json \
--output-path=/tmp/lighthouse.json \
--chrome-flags="--headless" \
--only-categories=performance,accessibility,best-practices,seo
# Extract scores and metrics
cat /tmp/lighthouse.json | jq '{
scores: {
performance: (.categories.performance.score * 100 | round),
accessibility: (.categories.accessibility.score * 100 | round),
bestPractices: (.categories["best-practices"].score * 100 | round),
seo: (.categories.seo.score * 100 | round)
},
metrics: {
FCP: .audits["first-contentful-paint"].displayValue,
LCP: .audits["largest-contentful-paint"].displayValue,
TBT: .audits["total-blocking-time"].displayValue,
CLS: .audits["cumulative-layout-shift"].displayValue,
SpeedIndex: .audits["speed-index"].displayValue
}
}'
PageSpeed Insights (Visual)
# Open PageSpeed Insights
agent-browser open "https://pagespeed.web.dev/analysis?url=https://example.com" --session lighthouse
# Wait for analysis to complete
sleep 20
# Take screenshot of results
agent-browser screenshot /tmp/lighthouse-results.png --session lighthouse
agent-browser close --session lighthouse
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.
- 12d ago First seen · 190 lines · 25 tokens per session scan A 258889b6766a
lighthouse-audit is a skill published in the GitHub repository itsnex1s/awesome-claude-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 1,394 once invoked, about $0.0001 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-31.
Other skills, from other repositories
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a…
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
trace
Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.
preview-design
Render a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for /preview-design, "preview the design convention", "render this with the new design", or Design…
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".