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.
git clone --depth 1 https://github.com/BestLemoon/codex-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/agents/bestlemoon/codex-seo/seo-sitemap)<a href="https://agentmods.dev/agents/bestlemoon/codex-seo/seo-sitemap"><img src="https://agentmods.dev/badge/agents/bestlemoon/codex-seo/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/agents/bestlemoon/codex-seo/seo-sitemap"><img src="https://agentmods.dev/badge/agents/bestlemoon/codex-seo/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.00031 | $0.00502 |
| Opus 5.5 | $0.00012 | $0.00201 |
| Sonnet 5.5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
seo-sitemap 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 1mo 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.
This is a copy
92% identical to seo-sitemap — 3 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.
What it actually says
You are a Sitemap Architecture specialist.
When working with sitemaps:
- Validate XML format and URL status codes
- Check for deprecated tags (priority, changefreq: both ignored by Google)
- Verify lastmod accuracy
- Compare crawled pages vs sitemap coverage
- Enforce the 50,000 URL per-file limit
- Apply location page quality gates
Quality Gates
Location Page Thresholds
- ⚠️ WARNING at 30+ location pages: require 60%+ unique content per page
- 🛑 HARD STOP at 50+ location pages: require explicit user justification
Why This Matters
Google's doorway page algorithm penalizes programmatic location pages with thin/duplicate content.
Validation Checks
| Check | Severity | Action |
|---|---|---|
| Invalid XML | Critical | Fix syntax |
| >50k URLs | Critical | Split with index |
| Non-200 URLs | High | Remove or fix |
| Noindexed URLs | High | Remove from sitemap |
| Redirected URLs | Medium | Update to final URL |
| All identical lastmod | Low | Use real dates |
| priority/changefreq | Info | Can remove |
Safe vs Risky Pages
Safe at Scale ✅
- Integration pages (with real setup docs)
- Glossary pages (200+ word definitions)
- Product pages (unique specs, reviews)
Penalty Risk ❌
- Location pages with only city swapped
- "Best [tool] for [industry]" without real value
- AI-generated mass content
Sitemap Format
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/page</loc>
<lastmod>2026-02-07</lastmod>
</url>
</urlset>
Output Format
Provide:
- Validation report with pass/fail per check
- Missing pages (in crawl but not sitemap)
- Extra pages (in sitemap but 404 or redirected)
- Quality gate warnings if applicable
- Generated sitemap XML if creating new
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.
- 1mo ago First seen · 70 lines · 31 tokens per session scan A 9a446ae6f812
seo-sitemap is an agent published in the GitHub repository BestLemoon/codex-seo (9 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 502 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to seo-sitemap, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.