lighthouse-pagespeed-wasp-drone — Claude Code subagent: what it does
lighthouse-pagespeed-wasp-drone is a subagent for Claude Code, Codex, and Cursor covering Lighthouse and PageSpeed Insights. It runs audits locally and in CI and explains score gaps.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install browser-and-app-testing-tools@wasp-nestWhat lighthouse-pagespeed-wasp-drone does
This subagent owns the measurement surface: Lighthouse runs via CLI, Node module, and DevTools, LHCI 0.15.x setup in GitHub Actions, interpreting the audit categories (Performance, Accessibility, Best Practices, SEO — the PWA category was dropped in Lighthouse 12), score budgets, and custom plugin authoring. It works from a companion skill, lighthouse-pagespeed-stinger, which indexes its guides.
The procedure is strict: throttling and form-factor are always set explicitly, at least three runs per measurement with the median reported, and lab numbers are reconciled against CrUX field data from the PSI API. One rule stands out — a clean TBT says nothing about INP, since INP covers the whole interaction lifecycle. Budgets are set off a measured baseline with a 10-20% buffer, never below production's current score without a fix plan.
Boundaries are explicit: SEO content work goes to seo-aeo-wasp-drone, Core Web Vitals fixes to react-wasp-drone, pipeline topology to devops-wasp-drone. Lighthouse plugins cannot use custom Gatherers, so page-specific data collection needs a full custom config instead.
What it helps with
- set up Lighthouse CI with LHCI in GitHub Actions
- add a performance budget gate to a CI pipeline
- reconcile a 90 Lighthouse score with failing field LCP or INP
- author a custom Lighthouse plugin
- pick a tracking tool: self-hosted LHCI server, Treo, or SpeedCurve
Example prompts for the agent
- Set up Lighthouse CI for GitHub Actions in this repo
- Add a performance budget to CI so the build fails on regressions
How to install lighthouse-pagespeed-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install browser-and-app-testing-tools@wasp-nest2Manually: put the files in place
.claude/agents/lighthouse-pagespeed-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/lighthouse-pagespeed-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/lighthouse-pagespeed-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about lighthouse-pagespeed-wasp-drone
How do I install lighthouse-pagespeed-wasp-drone in Claude Code?
Through the plugin marketplace: first run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install browser-and-app-testing-tools@wasp-nest. The agent lands as .claude/agents/lighthouse-pagespeed-wasp-drone.md.
What does lighthouse-pagespeed-wasp-drone do?
It runs Lighthouse audits locally and in CI, configures LHCI and performance budgets, reconciles lab scores with CrUX field data, and authors custom Lighthouse plugins.
Why doesn't a good TBT guarantee a good INP?
TBT only captures long tasks during page load, while INP measures the full interaction lifecycle across the session. A page can post TBT under 200ms yet field INP above 500ms, which is why the agent checks both.