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/kabde/seo-skills/seo-technicalgit clone --depth 1 https://github.com/kabde/seo-skillsWrote 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/kabde/seo-skills/seo-technical)<a href="https://agentmods.dev/agents/kabde/seo-skills/seo-technical"><img src="https://agentmods.dev/badge/agents/kabde/seo-skills/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.00562 |
| Opus 5 | $0.00017 | $0.00281 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
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 6d 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.
This is a copy
86% identical to seo-technical — 9 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.
What it actually says
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 Integration
- For AI search readiness, defer to the
seo-geosub-skill. - For schema validation, defer to the
seo-schemasub-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.
- 6d ago First seen · 54 lines · 35 tokens per session scan A 391d7a2e8526
seo-technical is an agent published in the GitHub repository kabde/seo-skills (11 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 562 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to seo-technical, differing in 9 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.