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 PavloSEO/seohead-seotools --skill sf-configgit clone --depth 1 https://github.com/PavloSEO/seohead-seotoolsWrote 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/pavloseo/seohead-seotools/sf-config)<a href="https://agentmods.dev/skills/pavloseo/seohead-seotools/sf-config"><img src="https://agentmods.dev/badge/skills/pavloseo/seohead-seotools/sf-config/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/pavloseo/seohead-seotools/sf-config"><img src="https://agentmods.dev/badge/skills/pavloseo/seohead-seotools/sf-config.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.00157 | $0.00973 |
| Opus 5 | $0.00078 | $0.00487 |
| Sonnet 5 | $0.00031 | $0.00195 |
| Haiku 4.5 | $0.00016 | $0.00097 |
Grade A, and why
sf-config 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SF Config — Configure Screaming Frog Once for Every Site
SF calculates some checks only when the corresponding modules are enabled.
They are disabled by default -> the report honestly marks those checks as
skipped (instead of falsely reporting zero). To maximize the checks that can run
from the 96-check registry in a single --crawl run, create an
audit.seospiderconfig profile once; the tool will then load it automatically.
Site type, crawl scope, and available exports still determine which checks apply.
The
.seospiderconfigformat is binary and can be created only by SF itself (it cannot be generated programmatically). Therefore, the step below must be completed manually once in the SF GUI (~1 minute).
Step 1 — Enable the Modules in SF (Once)
Open Screaming Frog, go to the Configuration menu, and enable:
- Spelling & Grammar ->
Configuration → Content → Spelling & Grammar-> Enable (+ select a language) -> unlocksSPELLING_ERRORS,GRAMMAR_ERRORS,LONG_SENTENCES,READABILITY_DIFFICULT(the columns appear in Internal:All). - Structured Data ->
Configuration → Spider → Extraction → Structured Data-> enable JSON-LD + Microdata + RDFa + Schema.org Validation + Google Rich Results -> unlocksSCHEMA_VALIDATION_ERROR,STRUCTURED_DATA_MISSING. - Security -> the Security tab is populated during a normal crawl, but for
resources, enable
Configuration → Spider → Crawl → Check Links Outside of Start Folderand rendering (below) -> unlocksMIXED_CONTENT,MISSING_HSTS. - Store HTML + Rendered HTML ->
Configuration → Spider → Extraction → Store HTMLandStore Rendered HTML-> unlocksDOM_TOO_DEEP,DOM_TOO_MANY_NODES(pass the directory through--configduring the crawl +input.html_store_dir). - JavaScript Rendering ->
Configuration → Spider → Rendering → JavaScript-> for SPA/Next.js sites; otherwise, the raw HTML contains less content. - Crawl Linked XML Sitemaps ->
Configuration → Spider → Crawl → XML Sitemaps-> Crawl Linked XML Sitemaps -> populates theSitemaps:*tabs (Orphan, Non-200 URLs in the sitemap). - Crawl Analysis (automatic) ->
Crawl Analysis → Configure → Auto Analyse At End of Crawl-> without it, Near Duplicates, Orphan URLs, and Link Score are empty.
What ships with it
1 file 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 · 74 lines · 157 tokens per session scan A e1a89ec25d04
sf-config is a skill published in the GitHub repository PavloSEO/seohead-seotools (0 stars, last pushed 8d ago), licensed MIT. It adds 157 tokens to every session and 973 once invoked, about $0.0008 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 skills, from other repositories
fire-your-seo-agency
A procedure for improving how a website appears in search engines and how AI answer systems find and cite it. It covers search, answer-engine, generative-AI, and Naver visibility.
geo-loop
Run one bounded eGEOagents loop iteration over a workspace domain - read the charter and fresh collector data, do ONE unit of work, write substrate artifacts, append one Timeline entry and one LOG line. Use for loop mode, /geo:loop, scheduled GEO runs, or continuous monitoring.
content-scoring
Score content against the 10 GEO criteria with evidence and prioritized fixes. Use when users ask to score, rate, evaluate, or estimate ranking strength.
competitive-analysis
Analyze AI-search competitors for a query and recommend ranking strategy. Use when users ask competitor analysis, who ranks, or competitive landscape.
validation-doctor
Check Brave Search and Chrome DevTools MCP availability and provide exact setup snippets. Use when validation dependencies are missing or uncertain.
geo-content-research
Researches what prompts people ask AI engines (ChatGPT, Gemini, Perplexity, Claude) about a product category and produces a prompts.csv artifact — a prioritized, strictly-schema'd list of the queries where the brand should be cited. Feeds the monitor workflow.