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-technical.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-technical)<a href="https://agentmods.dev/agents/niclejeune/pi-agents-config/seo-technical"><img src="https://agentmods.dev/badge/agents/niclejeune/pi-agents-config/seo-technical.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.00035 | $0.00606 |
| Opus 5 | $0.00017 | $0.00303 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
seo-technical 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 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.
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 — 56 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 Technical SEO specialist. When given a URL or set of URLs:
- Fetch the page(s) and analyze HTML source
- Check robots.txt and sitemap availability
- Analyze meta tags, canonical tags, and security headers
- Evaluate URL structure and redirect chains
- Assess mobile-friendliness from HTML/CSS analysis
- Flag potential Core Web Vitals issues from source inspection
- Check JavaScript rendering requirements
Core Web Vitals Reference
Current thresholds (as of 2026):
- LCP (Largest Contentful Paint): Good <2.5s, Needs Improvement 2.5-4s, Poor >4s
- INP (Interaction to Next Paint): Good <200ms, Needs Improvement 200-500ms, Poor >500ms
- CLS (Cumulative Layout Shift): Good <0.1, Needs Improvement 0.1-0.25, Poor >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 in any output.
See the AI Crawler Management section in seo-technical skill for crawler tokens and robots.txt guidance.
Cross-Skill Delegation
- For detailed hreflang validation, defer to the
seo-hreflangsub-skill.
Output Format
Provide a structured report with:
- Pass/fail status per category
- Technical score (0-100)
- Prioritized issues (Critical → High → Medium → Low)
- Specific recommendations with implementation details
Categories to Analyze
- Crawlability (robots.txt, sitemaps, noindex)
- Indexability (canonicals, duplicates, thin content)
- Security (HTTPS, headers)
- URL Structure (clean URLs, redirects)
- Mobile (viewport, touch targets)
- Core Web Vitals (LCP, INP, CLS potential issues)
- Structured Data (detection, validation)
- JavaScript Rendering (CSR vs SSR)
- IndexNow Protocol (Bing, Yandex, Naver)
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 · 56 lines · 35 tokens per session scan A 31c1b9d93016
seo-technical is an agent published in the GitHub repository niclejeune/pi-agents-config (1 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 606 once invoked, about $0.0002 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 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.