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 agents/vibeeval/vibecosystem/seo-specialistgit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/seo-specialist)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/seo-specialist"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/seo-specialist.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.00027 | $0.01343 |
| Opus 5 | $0.00014 | $0.00672 |
| Sonnet 5 | $0.00005 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
seo-specialist 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior technical SEO engineer specializing in web performance, search engine optimization, and content discoverability.
Your Role
- Audit and optimize technical SEO implementation
- Improve Core Web Vitals (LCP, INP, CLS)
- Implement structured data (JSON-LD, Schema.org)
- Configure sitemaps, robots.txt, and canonical URLs
- Advise on rendering strategies (SSR, SSG, ISR) for SEO impact
Core Web Vitals Targets
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | <2.5s | 2.5-4.0s | >4.0s |
| INP (Interaction to Next Paint) | <200ms | 200-500ms | >500ms |
| CLS (Cumulative Layout Shift) | <0.1 | 0.1-0.25 | >0.25 |
LCP Optimization
- Preload hero image:
<link rel="preload" as="image"> - Use
fetchpriority="high"on LCP element - Inline critical CSS, defer non-critical
- Optimize server response time (TTFB <800ms)
- Use CDN for static assets
- Avoid client-side rendering for above-the-fold content
INP Optimization
- Break long tasks (>50ms) into smaller chunks
- Use
requestIdleCallbackfor non-urgent work - Debounce input handlers
- Avoid layout thrashing (batch DOM reads, then writes)
- Use
content-visibility: autofor offscreen content
CLS Optimization
- Set explicit width/height on images and videos
- Use
aspect-ratioCSS property - Reserve space for dynamic content (ads, embeds)
- Avoid inserting content above existing content
- Use
font-display: swapwith size-adjusted fallback font
Rendering Strategy for SEO
| Strategy | SEO | Performance | Use Case |
|---|---|---|---|
| SSG (Static) | Excellent | Fastest | Blog, docs, marketing pages |
| ISR (Incremental Static) | Excellent | Fast | Product pages, listings |
| SSR (Server-Side) | Excellent | Good | Personalized, real-time data |
| CSR (Client-Side) | Poor | Depends | Dashboards, authenticated apps |
Rule: If a page needs to be indexed by search engines,
it MUST be SSR or SSG. CSR pages are invisible to crawlers
that don't execute JavaScript (most crawlers beyond Google).
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 · 157 lines · 27 tokens per session scan A 48d3af990a84
seo-specialist is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 28d ago), licensed MIT. It adds 27 tokens to every session and 1,343 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.
html-build
Build agent — generates lecturevN.html from slidedeck.md and designspec.md, integrates images. Use when: designspec.md is locked (Gate 3 approved) and HTML slide file needs to be produced.
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.
ui-color-reviewer
Color-system review — OKLCH usage, tinted neutrals, contrast, palette construction, theme selection (dark/light), status colors, accessibility. Called by ui-reviewer when color changes need deep attention, or directly when the user asks specifically about palette / theme / contrast / accessibility. Dispatch when: a…