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 agentmods add skills/plugin87/full-stack-design-skills/web-performance-optimizationnpx skills add plugin87/full-stack-design-skills --skill web-performance-optimizationgit clone --depth 1 https://github.com/plugin87/full-stack-design-skillsWhat 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 | $0.00111 | $0.03887 |
| Opus 5 | $0.00056 | $0.01944 |
| Sonnet 5 | $0.00022 | $0.00777 |
| Haiku 4.5 | $0.00011 | $0.00389 |
Grade A, and why
web-performance-optimization 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 2d 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 — 514 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Performance Optimization
A practical guide to measuring, diagnosing, and improving web application performance.
Performance is a user experience feature. A fast site converts better, keeps users engaged, and ranks higher in search. This skill covers the metrics that matter, tools that measure them, and concrete optimization strategies.
Core Web Vitals: The Three Metrics That Matter
Google's Core Web Vitals are the three quantitative measures of user experience. They directly impact search rankings and user satisfaction.
1. Largest Contentful Paint (LCP)
What it measures: How fast the largest visible element (text, image, video) appears on screen.
Target: < 2.5 seconds
Why it matters: Users perceive "fast" as "appears quickly." If the main content takes 4+ seconds, users bounce.
What counts as LCP:
<img>elements<image>inside<svg>- Backgrounds with
background-image - Text blocks (paragraphs, headings)
- Videos (poster frame)
- Canvas elements
What doesn't count:
- Off-screen images
- Transparent images
- Text in canvas
Example LCP Timeline:
0s — Page begins to load
0.8s — Hero image starts loading
1.2s — Hero image finishes (LCP = 1.2s) ✓ Good (< 2.5s)
2.1s — Page fully interactive
Optimization strategies:
- Preload critical images (
<link rel="preload">) - Compress images aggressively (WebP format, lazy loading for below-the-fold)
- Use a CDN for fast global delivery
- Avoid render-blocking CSS/JavaScript
- Use server-side rendering for critical content
2. First Input Delay (FID) → Interaction to Next Paint (INP)
What it measures: Delay between user input (click, tap, keystroke) and browser response.
Target: < 100ms (FID) or < 200ms (INP)
Why it matters: Slow response feels like the app is frozen. Users think something broke and abandon the interaction.
FID vs. INP:
- FID (First Input Delay): Only measures the first user interaction. Being fast once doesn't mean consistently fast.
- INP (Interaction to Next Paint): Measures all interactions throughout the page lifetime. More realistic; now recommended over FID.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 514 lines · 0 tokens per session scan A 66646e1beaf7
web-performance-optimization is a skill published in the GitHub repository plugin87/full-stack-design-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 3,887 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…