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 skills add lisbeth718/pseo-skills --skill seo-log-analysisgit clone --depth 1 https://github.com/lisbeth718/pseo-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/skills/lisbeth718/pseo-skills/seo-log-analysis)<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/seo-log-analysis"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/seo-log-analysis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/seo-log-analysis"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/seo-log-analysis.svg" alt="Reviewed on agentmods" width="80" 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.00071 | $0.04085 |
| Opus 5.5 | $0.00028 | $0.01634 |
| Sonnet 5.5 | $0.00014 | $0.00817 |
| Haiku 4.5 | $0.00007 | $0.00409 |
Grade A, and why
seo-log-analysis 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Google range files (all return 200, checked 2026-10-12 with `curl -sI`), under `https://developers.google.com/static/crawling/ipranges/`: How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Log Analysis
Logs are the only first-party record of what crawlers actually fetch. Search Console shows samples; logs show everything. Use them to turn "Discovered - currently not indexed" into a specific cause and action.
Read-only skill: it produces findings and recommended changes, it does not edit config.
1. Get the logs
| Source | How | Notes |
|---|---|---|
| nginx | access_log with the seo JSON format below |
$request_time is total time, not TTFB; for TTFB use $upstream_header_time (origin) |
| Caddy | log { format json } |
Fields: request.uri, request.remote_ip, request.headers["User-Agent"], status, duration (seconds), size |
| Traefik | accessLog: { format: json, fields: { headers: { defaultMode: keep } } } |
Fields: RequestPath, ClientHost, DownstreamStatus, Duration (nanoseconds), request_User-Agent |
| Cloudflare | Logpush http_requests dataset to R2/S3 (NDJSON). Enterprise plans only; other plans need a Worker or origin logs |
ClientRequestURI, ClientIP, ClientRequestUserAgent, EdgeResponseStatus, EdgeTimeToFirstByteMs, CacheCacheStatus, VerifiedBotCategory. Edge logs include cache hits, origin logs do not |
| Vercel | Log Drain (HTTP/Datadog/etc.) | Runtime logs are kept only 1h (Hobby) or 1 day (Pro), so a drain is the only way to get history. Request entries carry a proxy object: proxy.path (with query), proxy.statusCode, proxy.userAgent (an array, take element 0), proxy.clientIp, proxy.method, proxy.vercelCache, proxy.responseByteSize; top-level timestamp is epoch ms. Filter to entries with proxy set (checked 2026-10-12 against vercel.com/docs/drains/reference/logs; re-check before relying on it) |
If the origin sits behind a CDN, analyze edge logs for crawl volume and origin logs for response time. Real client IP must come from the CDN header, never from the proxy hop.
Minimum window: 14 days for patterns, 30+ for template-level crawl share. Keep raw logs outside the repo and strip user IPs from anything committed.
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 · 241 lines · 71 tokens per session scan A a417fcea8150
seo-log-analysis is a skill published in the GitHub repository lisbeth718/pseo-skills (54 stars, last pushed 6d ago), licensed MIT. It adds 71 tokens to every session and 4,085 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.