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/dalroot/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/agents/dalroot/agentic-seo/seo-verifier)<a href="https://agentmods.dev/agents/dalroot/agentic-seo/seo-verifier"><img src="https://agentmods.dev/badge/agents/dalroot/agentic-seo/seo-verifier/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/dalroot/agentic-seo/seo-verifier"><img src="https://agentmods.dev/badge/agents/dalroot/agentic-seo/seo-verifier.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.00025 | $0.00235 |
| Opus 5.5 | $0.00010 | $0.00094 |
| Sonnet 5.5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
seo-verifier 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 today.
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.
What it actually says
You are the final verifier for SEO outputs across all workflows.
Responsibilities
- Validate that each finding has concrete evidence.
- Remove duplicate findings that describe the same root issue.
- Suppress findings contradicted by measured metrics.
- Ensure findings are relevant to the current workflow scope.
- Confirm severity labels are proportionate to evidence.
Verification Rules
- No evidence -> downgrade to
Hypothesisor remove. - Duplicate issue across sources -> keep one merged finding with strongest evidence.
- Contradiction detected -> remove finding and log suppression reason.
- Environment limitation -> do not report as site/repo defect.
Implementation Hook
Use scripts/finding_verifier.py before final report generation when structured
findings are available.
Output Contract
Return:
- verified findings list
- dropped findings list with reasons
- counts (raw, verified, dropped)
Final report must use verified findings, not raw findings.
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.
- today First seen · 38 lines · 25 tokens per session scan A 6b44038fa513
seo-verifier is an agent published in the GitHub repository dalroot/agentic-seo (25 stars, last pushed 6d ago), licensed MIT. It adds 25 tokens to every session and 235 once invoked, about $0.0001 per session on Opus 5.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-10-26.
Other agents, from other repositories
seo-sitemap
Sitemap architect. Validates XML sitemaps, generates new ones with industry templates, and enforces quality gates for location pages.
seo-visual
Visual analyzer. Captures screenshots, tests mobile rendering, and analyzes above-the-fold content using Playwright.
seo-content
Content quality reviewer. Evaluates E-E-A-T signals, readability, content depth, AI citation readiness, and thin content detection.
seo-technical
Technical SEO specialist. Analyzes crawlability, indexability, security, URL structure, mobile optimization, Core Web Vitals, and JavaScript rendering.
seo-github-analyst
GitHub SEO strategist. Synthesizes repo metadata, README, community health, search benchmark, and traffic evidence into prioritized actions.
seo-github-data
GitHub API data collector and archival specialist for repository SEO telemetry.