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-reportgit 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-report)<a href="https://agentmods.dev/skills/pavloseo/seohead-seotools/sf-report"><img src="https://agentmods.dev/badge/skills/pavloseo/seohead-seotools/sf-report/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-report"><img src="https://agentmods.dev/badge/skills/pavloseo/seohead-seotools/sf-report.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.00117 | $0.00695 |
| Opus 5 | $0.00059 | $0.00347 |
| Sonnet 5 | $0.00023 | $0.00139 |
| Haiku 4.5 | $0.00012 | $0.00069 |
Grade A, and why
sf-report 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SF Report — Readable Report from a Screaming Frog Export
Converts an SF export (CSV/XLSX) or an existing audit.json into a human-readable
audit.md and helps review it with the user. It uses the same engine as
sf-analyzer, but the goal here is not diagnostics for the sake of JSON; it is a
clear report.
When to Use It
- "Create a readable report from this SF export";
- "Format an audit report for the client / developers";
- "Explain
audit.jsonin plain language and identify what matters."
Workflow
- Identify the input: a directory containing SF exports (at minimum
Internal:All) or an existingaudit.json. If only a.seospiderfile is available, see../sf-analyzer/SKILL.md(this requires the SF CLI or a manual CSV export). - Generate the report:
The generatedseohead sf run --exports-dir ./exports --out ./report --format md,jsonreport/audit.mdis the readable report. Ifaudit.jsonalready exists, rebuild the Markdown with the same run when necessary. - Review it with the user according to the
audit.mdstructure:- Health summary — health score, severity table, top issues, HTML weight;
- Critical — broken links (table
Destination｜Source｜Anchor｜Position｜XPath), 5xx responses, 4xx/5xx URLs in the sitemap, redirect loops; - Warning — duplicates (grouped), multiple H1 elements with their text, canonical issues, thin content, sitemap mismatches, heavy HTML (× median);
- Notice — URL hygiene, meta-field lengths;
- Sitemap & robots — sitemaps, mismatches,
lastmoddistribution.
- Highlight what matters: start with critical issues and the most frequent
problems (
summary.by_check); explain the impact and what to fix (thefix_hintfield). Do not dump the entire list — highlight the priorities and attach the rest as a file. - Attach
report/audit.md(+audit.json) for download.
Interpretation
- Check registry and severity levels —
../sf-analyzer/reference/checks.md. audit.jsoncontract —../sf-analyzer/reference/json_schema.md.- If tasks/a backlog are needed from the report, switch to the
sf-tasksskill.
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 · 55 lines · 117 tokens per session scan A 695f42ded9df
sf-report is a skill published in the GitHub repository PavloSEO/seohead-seotools (0 stars, last pushed 8d ago), licensed MIT. It adds 117 tokens to every session and 695 once invoked, about $0.0006 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.