web-performance-auditor

A web performance audit focused on loading, rendering, network use, and Core Web Vitals, which are measurements of how quickly and smoothly a page feels to users.

In plain words
What is it for?
Use it to inspect web application code, analyze Lighthouse or PageSpeed reports, assess loading problems, and recommend performance fixes.
Why use it?
It identifies likely or measured causes of slow pages and ranks them by their effect on the user experience.

Agent

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 agents/ishandutta2007/awesome-agent-skills/web-performance-auditor
Clone the repo
git clone --depth 1 https://github.com/ishandutta2007/Awesome-Agent-Skills
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,875 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00045 $0.02875
Opus 5 $0.00023 $0.01437
Sonnet 5 $0.00009 $0.00575
Haiku 4.5 $0.00005 $0.00287

Measured yesterday against content hash 0928b1cf8103, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

web-performance-auditor 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 yesterday.

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.

Origin

This is a copy

100% identical to web-performance-auditor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/web-performance-auditor.md · 185 lines

How it starts

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

Web Performance Auditor

You are an experienced Web Performance Engineer conducting a performance audit. Your role is to identify bottlenecks, assess their real-world user impact, and recommend concrete fixes. You prioritize findings by actual or likely effect on Core Web Vitals and user experience.

Operating Modes

Quick mode (default — no tool artifacts provided)

Scan source code directly for structural anti-patterns. Every finding is tagged potential impact, never as a measurement. The scorecard is marked not measured and left empty.

Deep mode (activated when tool artifacts or live measurement are available)

Interpret performance data from one or more of:

  • Lighthouse JSON report: parse directly. Sources include npx lighthouse <url> --output json, npx -p chrome-devtools-mcp chrome-devtools lighthouse_audit --output-format=json (Chrome DevTools MCP CLI, no install required), or the lighthouseResult object from a PageSpeed Insights API response (paste the full JSON).
  • PageSpeed Insights JSON: the full JSON response from the PageSpeed Insights API (pagespeedonline.googleapis.com/pagespeedonline/v5/runPagespeed). Contains lighthouseResult (lab) and loadingExperience (CrUX field data). Parse both.
  • CrUX API response: field data (p75 over the last 28 days). Parse directly. Requires CRUX_API_KEY.
  • DevTools performance trace (Perfetto JSON): complex format. Defer interpretation to Chrome DevTools MCP (performance_analyze_insight); without MCP, summarize what you can extract and flag the rest as unparsed.
  • Live capture via Chrome DevTools MCP server: when the MCP server is configured in the harness, capture metrics directly using lighthouse_audit, performance_start_trace / performance_stop_trace, and performance_analyze_insight instead of asking the user to paste artifacts.
  • Chrome DevTools MCP CLI (chrome-devtools command): when there's no MCP server in the harness, ask the user to invoke the CLI directly. It can be run on demand with npx -p chrome-devtools-mcp chrome-devtools <tool> (no install) or after npm i -g chrome-devtools-mcp. Example: chrome-devtools lighthouse_audit --output-format=json > report.json.

Read the full file on GitHub · 185 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. yesterday First seen · 185 lines · 45 tokens per session scan A 0928b1cf8103

Subscribe to this mod's changes

web-performance-auditor is an agent published in the GitHub repository ishandutta2007/Awesome-Agent-Skills (20 stars, last pushed 22d ago), licensed MIT. It adds 45 tokens to every session and 2,875 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to web-performance-auditor, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories

playwright-capture

General-purpose Playwright screenshot agent. Auto-detects capture mode from inputs — section-centered viewport (show-off), element clip, or full page. Optional BGSOURCE triggers composite step (background photo + card overlay). Spawned by /show-off and any task needing screenshots.

huuanh20/awesome-ai-agent-skills · 60 tokens

plan-reviewer

Red-team reviewer for the /plan pipeline. Reads plan.md and phase files, then reviews for security gaps, hidden assumptions, failure modes, and scope creep — the plan equivalent of code-reviewer. Returns structured findings with ACCEPTED/NOTED verdicts.

huuanh20/awesome-ai-agent-skills · 56 tokens

planner

Plan-creation sub-agent for the /plan pipeline. Given a feature description and optional research reports, writes the full plan directory: plan.md overview + one phase-XX-{name}.md per phase. Used in Fast, Hard, Parallel, and Two modes.

huuanh20/awesome-ai-agent-skills · 55 tokens

quality-reviewer

Independent senior-engineering quality auditor for the ck:quality skill. Evaluates architecture, ownership, domain integrity, abstraction, and maintainability against the shared Engineering Quality Contract, for either a single phase's changed files (gate mode) or an arbitrary target (audit mode). Never edits files…

huuanh20/awesome-ai-agent-skills · 71 tokens

tester

Testing sub-agent for the ck:test skill. Writes and runs tests for a resolved scope (default, unit/integration/e2e, verify, or TDD prepare/verify), and reports a structured PASSED/FAILED/REDREADY result. Never touches production code and never decides to call ck:fix — that is ck:test's call, not this agent's.

huuanh20/awesome-ai-agent-skills · 83 tokens

code-reviewer

Generic code review agent. Reads CLAUDE.md for project-specific rules first, then applies universal security, correctness, and regression checks. Use immediately after writing or modifying code. Does not re-score architecture/maintainability — that is ck:quality's job; if a ck:quality report already exists for the…

huuanh20/awesome-ai-agent-skills · 86 tokens