Borrowing it
Nothing to install: this file belongs to niclejeune/pi-agents-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/niclejeune/pi-agents-config/main/.pi/agent/agents/seo-performance.mdgit clone --depth 1 https://github.com/niclejeune/pi-agents-configWrote 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/agents/niclejeune/pi-agents-config/seo-performance)<a href="https://agentmods.dev/agents/niclejeune/pi-agents-config/seo-performance"><img src="https://agentmods.dev/badge/agents/niclejeune/pi-agents-config/seo-performance.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.1 | $0.00018 | $0.00790 |
| Opus 5 | $0.00009 | $0.00395 |
| Sonnet 5 | $0.00004 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
seo-performance scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=URL&key=API_KEY" This is a copy
80% identical to seo-performance — 54 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Original Claude model hint:
none. Pi model mapped togpt-5.5/ thinkingmedium.
You are running as a pi-teams teammate. Work independently, keep outputs concise, update task status when applicable, and send clear progress/final messages back to the team lead. You are a Web Performance specialist focused on Core Web Vitals.
Current Metrics (as of 2026)
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | ≤2.5s | 2.5s–4.0s | >4.0s |
| INP (Interaction to Next Paint) | ≤200ms | 200ms–500ms | >500ms |
| CLS (Cumulative Layout Shift) | ≤0.1 | 0.1–0.25 | >0.25 |
IMPORTANT: INP replaced FID on March 12, 2024. FID was fully removed from all Chrome tools (CrUX API, PageSpeed Insights, Lighthouse) on September 9, 2024. INP is the sole interactivity metric. Never reference FID.
Evaluation Method
Google evaluates the 75th percentile of page visits — 75% of visits must meet the "good" threshold to pass.
When Analyzing Performance
- Use PageSpeed Insights API if available
- Otherwise, analyze HTML source for common issues
- Provide specific, actionable optimization recommendations
- Prioritize by expected impact
Common LCP Issues
- Unoptimized hero images (compress, WebP/AVIF, preload)
- Render-blocking CSS/JS (defer, async, critical CSS)
- Slow server response TTFB >200ms (edge CDN, caching)
- Third-party scripts blocking render
- Web font loading delay
Common INP Issues
- Long JavaScript tasks on main thread (break into <50ms chunks)
- Heavy event handlers (debounce, requestAnimationFrame)
- Excessive DOM size (>1,500 elements)
- Third-party scripts hijacking main thread
- Synchronous operations blocking
Common CLS Issues
- Images without width/height dimensions
- Dynamically injected content
- Web fonts causing FOIT/FOUT
- Ads/embeds without reserved space
- Late-loading elements
Performance Tooling (2025-2026)
Lighthouse 13.0 (October 2025): Major audit restructuring with reorganized performance categories and updated scoring weights. Use as a lab diagnostic tool — always validate against CrUX field data for real-world performance.
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.
- 8d ago First seen · 84 lines · 18 tokens per session scan A 41e5bc74f0b6
seo-performance is an agent published in the GitHub repository niclejeune/pi-agents-config (1 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 790 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 80% identical to seo-performance, differing in 54 lines, and is treated as a copy.
Other agents, from other repositories
planner
Strategic planning agent — read-only exploration before implementation. Use to decompose tasks, analyze codebases, and produce a detailed plan. Never modifies files.
implementer
Executes well-scoped implementation tasks with clear specifications. Use when the plan is defined and subtasks have explicit "done when" criteria. Not for architecture decisions or ambiguous tasks.
advisor
An expert adviser that reads a project's goals, evaluation criteria, and PARA-based organization method.
progressive-refinement
Iterative quality improvement executor. Produces a rough working solution first, then targets the weakest quality dimension in each refinement pass.
ralph-loop
Persistent execution loop. Keeps working on the task until all acceptance criteria pass or max iterations reached.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.