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/shandar/pwp-plugin/pwp-perfnpx skills add shandar/pwp-plugin --skill pwp-perfgit clone --depth 1 https://github.com/shandar/pwp-pluginWrote 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/shandar/pwp-plugin/pwp-perf)<a href="https://agentmods.dev/skills/shandar/pwp-plugin/pwp-perf"><img src="https://agentmods.dev/badge/skills/shandar/pwp-plugin/pwp-perf.svg" alt="Measured on agentmods" 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 | $0.00113 | $0.00900 |
| Opus 5 | $0.00056 | $0.00450 |
| Sonnet 5 | $0.00023 | $0.00180 |
| Haiku 4.5 | $0.00011 | $0.00090 |
Grade A, and why
pwp-perf 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Optimization Skill
The cardinal rule: never optimize on vibes. Measure, identify the bottleneck, fix it, prove it's faster.
Performance Mindset
- Measure before optimizing. Intuition about performance is wrong more often than right. Profile first.
- Optimize the bottleneck. Making a fast operation faster doesn't help.
- Premature optimization is real. Only optimize measured problems or known-critical paths.
- Verify the improvement. Before/after numbers or it didn't happen.
Investigation Protocol
Step 1: Define the Problem
- What is slow? (Page load, API, render, build)
- How slow? (Actual numbers: "3.2 seconds")
- What is the target? ("Under 1 second")
Step 2: Measure Current State
| Area | How to Measure |
|---|---|
| Page load | Lighthouse, DevTools Performance tab |
| Core Web Vitals | LCP, INP, CLS via Lighthouse |
| API response | Network tab timing, server-side logging |
| Render | React DevTools Profiler |
| Bundle size | Build output, bundlephobia |
| Memory | DevTools Memory tab, heap snapshots |
| Database | Query EXPLAIN plans |
Step 3: Identify the Bottleneck
- Network — too many requests, large payloads, no caching
- Data — slow queries, over-fetching, N+1 patterns
- Rendering — unnecessary re-renders, layout thrashing
- Compute — expensive calculations on main thread
- Assets — uncompressed images, unminified JS
Step 4: Fix the Bottleneck
| Bottleneck | Common Fixes |
|---|---|
| Large bundle | Code splitting, dynamic imports, tree shaking |
| Slow page load | Lazy loading, preload critical resources |
| Re-renders | useMemo, useCallback, React.memo (only where profiled) |
| Slow API | Caching, pagination, field selection |
| N+1 queries | Batch queries, eager loading, DataLoader |
| Large images | WebP/AVIF, responsive srcset, lazy loading |
| Heavy computation | Web Workers, caching results |
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.
- 3d ago First seen · 85 lines · 113 tokens per session scan A 03735325080a
pwp-perf is a skill published in the GitHub repository shandar/pwp-plugin (1 stars, last pushed 6mo ago), licensed MIT. It adds 113 tokens to every session and 900 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
glossary-init
USE WHEN setting up a repo for AI-first work, when an agent hallucinates domain term meaning, or when user asks to bootstrap / extend the repo's domain glossary. Surfaces candidate terms by identifier frequency, asks the user for 1-sentence definitions, writes GLOSSARY.md at repo root. Idempotent — re-running adds new…
status
Set a status message on your DevGlobe profile.
codex-pair-resume
Resume codex-pair for this project after a previous pause. Removes .codex-pair/state/paused and clears failure state. Review resumes on the next supported file edit; missing state is a no-op.
conventions-init
USE WHEN setting up a repo for AI-first work (after /init-repo), or when the context-surface hook should start feeding repo conventions to agents before edits. Drafts conventions.yml at repo root: per-kind casing (inferred from the code), a vague-name denylist seed, directory roles, and a hand-filled house-rules…
opik
This skill should be used when the user needs to add Opik tracing or integrations to their code, instrument an LLM application, or needs reference for Opik SDK usage (Python, TypeScript, REST API). Use for tasks like "add tracing", "instrument my code", "use trackopenai", "add OpikTracer", "what span types are…
codex-review
Get a second opinion from OpenAI Codex on your current code changes. Analyzes staged/unstaged diffs and returns prioritized findings. Use when user asks to "review with Codex", "Codex code review", or "ask Codex to check my code".