seo-verifier

seo-verifier is an agent for Claude Code from buithang3058/Agentic-SEO. It costs 25 tokens per session (235 once invoked), scanned A, a copy of seo-verifier, MIT.

A final checker for SEO findings that verifies evidence, removes duplicates and contradictions, and adjusts unsupported severity claims. SEO findings are reported issues that may affect how content performs in search.

In plain words
What is it for?
Use it to validate structured SEO findings, retain evidence-backed issues, downgrade unsupported claims to hypotheses, and produce verified and dropped-finding lists.
Why use it?
It prevents reports from presenting guesses, repeated issues, or claims contradicted by measured results as confirmed problems.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to validate structured SEO findings, retain evidence-backed issues, downgrade unsupported…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/buithang3058/agentic-seo/seo-verifier
Install

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.

Clone the repo
git clone --depth 1 https://github.com/buithang3058/Agentic-SEO

Made for: Claude Code.

Wrote 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.

agentmods badge for seo-verifier

README.md
[![agentmods](https://agentmods.dev/badge/agents/buithang3058/agentic-seo/seo-verifier.svg)](https://agentmods.dev/agents/buithang3058/agentic-seo/seo-verifier)
Your own site
<a href="https://agentmods.dev/agents/buithang3058/agentic-seo/seo-verifier"><img src="https://agentmods.dev/badge/agents/buithang3058/agentic-seo/seo-verifier.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 235 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00235
Opus 5 $0.00013 $0.00118
Sonnet 5 $0.00005 $0.00047
Haiku 4.5 $0.00003 $0.00023

Measured 6d ago against content hash 6b44038fa513, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 6d 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.

Origin

This is a copy

100% identical to seo-verifier — 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.

resources/agents/seo-verifier.md · 38 lines

What it actually says

You are the final verifier for SEO outputs across all workflows.

Responsibilities

  1. Validate that each finding has concrete evidence.
  2. Remove duplicate findings that describe the same root issue.
  3. Suppress findings contradicted by measured metrics.
  4. Ensure findings are relevant to the current workflow scope.
  5. Confirm severity labels are proportionate to evidence.

Verification Rules

  • No evidence -> downgrade to Hypothesis or 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.

Changes

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.

  1. 6d ago First seen · 38 lines · 25 tokens per session scan A 6b44038fa513

Subscribe to this mod's changes

seo-verifier is an agent published in the GitHub repository buithang3058/Agentic-SEO (2 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 235 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to seo-verifier, differing in 0 lines, and is treated as a copy.