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 T4wroot/agentic-seo --skill sitemapgit clone --depth 1 https://github.com/T4wroot/agentic-seoWrote 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/t4wroot/agentic-seo/sitemap)<a href="https://agentmods.dev/skills/t4wroot/agentic-seo/sitemap"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/sitemap/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/t4wroot/agentic-seo/sitemap"><img src="https://agentmods.dev/badge/skills/t4wroot/agentic-seo/sitemap.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.00091 | $0.03009 |
| Opus 5 | $0.00046 | $0.01504 |
| Sonnet 5 | $0.00018 | $0.00602 |
| Haiku 4.5 | $0.00009 | $0.00301 |
Grade A, and why
xml-sitemap 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 7d 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.
curl -I https://example.com/sitemap.xml # Check Content-Type This is a copy
100% identical to xml-sitemap — 0 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.
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Technical: Sitemap
Guides sitemap creation, auditing, and optimization for search engine discovery.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Scope (Technical SEO)
- Sitemap: Create XML sitemap; submit to Google Search Console
- URL discovery: Help search engines find pages; especially important for large sites or poor internal linking
Task
Generate an XML Sitemap that complies with the sitemaps.org protocol from the project's page list, and declare it in robots.txt.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site URL and page structure.
Identify:
- Site URL: Base domain (e.g.,
https://example.com) - URL count: Total indexable pages (single sitemap vs. sitemap index)
- Data source: Static config, CMS, file system, or hybrid
Precondition: Does the site need a sitemap?
Before generating, assess whether a sitemap is warranted. A sitemap is most valuable when:
- Large site (hundreds+ pages) or new site with few backlinks
- Deep or orphaned pages that internal links don't reach well
- Rich media (images, videos, news) needing extension metadata
- GSC shows growing "Discovered – not indexed" or "Not discovered" counts
Small sites (< 50 pages) with strong internal linking may not strictly need one, but creating a sitemap has near-zero cost and provides future-proof infrastructure. If in doubt, err on the side of creating.
1. Protocol Essentials
| Item | Spec |
|---|---|
| Single sitemap limit | 50,000 URLs, 50MB (uncompressed) |
| Sitemap index | When exceeding limit, split and have main index reference sub-sitemaps |
| Encoding | UTF-8 |
| URL format | Full URL, same host, include https:// |
| Required tags | <loc> |
| Optional tags | <lastmod>, <changefreq>, <priority> |
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.
- 7d ago First seen · 265 lines · 91 tokens per session scan A 53b74e2e2e11
xml-sitemap is a skill published in the GitHub repository T4wroot/agentic-seo (15 stars, last pushed 8d ago), licensed MIT. It adds 91 tokens to every session and 3,009 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to xml-sitemap, differing in 0 lines, and is treated as a copy.
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.
content-thicken
Evidence-driven blog driver. Takes ONE target from the fused search plus AI-answer content library, pulls the real questions it has to answer, drafts a thick long-form guide against a template contract, validates it deterministically, and stops at preview. Two modes, thicken an already-earning post IN PLACE (never…
backlink-outreach
Find, evaluate, pitch and track natural backlink and content partnerships. Prospects come from the GEO citation data rather than a generic blog search: the targets are the pages an AI already cites when answering your category questions. Research runs on the Monid tool layer (web search and scrape, authority metrics…
geo-monitor
Run and read the GEO pipeline, which measures whether AI answer engines mention, recommend and cite your site. Puts a fixed registry of real user questions to an answer engine through the Monid tool layer, detects the three signals plus competitors, and turns "a rival is named and we are not" into a tracked work…
seo-intake
Run and read the SEO intake pipeline. Pulls the organic keyword set for your domain and for each competitor through the Monid tool layer, computes the gap locally, and routes every keyword to the one action that can help it (write-new / striking / build-depth / defend / noise). Use when asked to refresh the SEO queue…
bing-duplicate-content-fix
Audit article groups, WordPress categories, or supplied URLs for copied content, near-duplicate templates, search-intent overlap, and keyword cannibalization; prepare exact SEO/AEO/GEO fixes; apply only approved WordPress changes; verify saved and public results; and request a Bing recrawl when authorized. Use for…