Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sergekostenchuk/seo-llm-skill-clusternpx agentmods add skills/sergekostenchuk/seo-llm-skill-cluster/server-log-crawler-analystWrote 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/sergekostenchuk/seo-llm-skill-cluster/server-log-crawler-analyst)<a href="https://agentmods.dev/skills/sergekostenchuk/seo-llm-skill-cluster/server-log-crawler-analyst"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/seo-llm-skill-cluster/server-log-crawler-analyst/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/sergekostenchuk/seo-llm-skill-cluster/server-log-crawler-analyst"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/seo-llm-skill-cluster/server-log-crawler-analyst.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.00090 | $0.00882 |
| Opus 5 | $0.00045 | $0.00441 |
| Sonnet 5 | $0.00018 | $0.00176 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
server-log-crawler-analyst 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- server-log-crawler-analyst — 100% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Server Log Crawler Analyst
Use this skill when credential-free monitoring evidence is enough, or when credentialed Search Console, rank tracking, analytics, or assistant citation tools are unavailable.
Read references/data-source-tiers.md before producing a monitoring report.
Owns
- credential-free monitoring baseline;
- server access-log summary with IP privacy protection;
- crawler/user-agent observation reports;
- public HTTP checks for robots, llms.txt, sitemaps, RSS, and representative URLs;
- data-source tiering;
- monitoring limitations and unknowns;
- backlog handoff for Search Console, rank/SERP, analytics, and LLM citation monitoring.
Does Not Own
- credentialed Search Console or analytics API work;
- scraping search engines;
- bypassing bot protections;
- live firewall or WAF changes;
- claims about rankings or assistant citations without direct evidence;
- storing raw IP logs in public artifacts.
Workflow
- Identify available evidence: public URL fetches, access-log snippet, exported summary, or synthetic fixture.
- Label the evidence tier and collection time.
- If logs are provided, summarize requests by path, status, user-agent class, and redacted IP hash.
- Separate known crawler hits from unknown bot-like traffic.
- Check public discovery endpoints when requested.
- Record limitations: no Search Console, no rank data, no assistant citation data unless explicitly provided.
- Produce a monitoring report using assets/crawler-monitor-report.template.md.
- Hand off credentialed or citation tasks to the backlog.
Non-Negotiables
- Do not publish raw IP addresses.
- Do not store credentials, cookies, API keys, or private analytics exports in skill files.
- Do not infer ranking, indexing, or citation success from server logs alone.
- Do not claim a user-agent is verified Google/OpenAI/Claude/Perplexity unless verification method is documented.
- Do not scrape SERPs or assistants against terms of service.
- Do not change firewall, WAF, robots, or server config from this skill.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 90 lines · 90 tokens per session scan A 5203a4a08912
server-log-crawler-analyst is a skill published in the GitHub repository sergekostenchuk/seo-llm-skill-cluster (39 stars, last pushed 3mo ago), licensed MIT. It adds 90 tokens to every session and 882 once invoked, about $0.0005 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-30.
Other skills, from other repositories
technocore-chat
Coordinate with other AI agents over plain HTTP GETs — shared rooms, durable notes, long-polling. No POST, no sockets, no client libraries, no account; a fetch tool is enough, and an MCP server fronts the same surface. Use when you need to leave a message for another agent, wait for one, or persist state across your…
dialectical-paper-writing
Analyze, design, write, revise, translate, and review empirical or technical research papers through an evidence-bounded dialectical workflow. Use when Codex must develop a research question, integrate reference papers with a user's ideas, build phenomenon-mechanism-conditions reasoning, design methods or experiments…
wiki-ingest
Compile a raw source (document, URL content, meeting notes, research output) into a wikikit agent wiki — merge-don't-overwrite, log contradictions, maintain cross-references, then lint. Use whenever the user says "add this to the wiki", "ingest this", or drops new source material for a wiki maintained with…
agent-pitbook
Search and contribute to Agent Pitbook, a structured debugging pit knowledge base for coding agents. Use when Codex is diagnosing recurring local-development failures, sandbox issues, dependency installation errors, Docker or port problems, MCP/tool quirks, browser automation failures, or when a verified debugging…
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.