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/Bhanunamikaze/Agentic-SEO-SkillWrote 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/bhanunamikaze/agentic-seo-skill/seo-verifier)<a href="https://agentmods.dev/agents/bhanunamikaze/agentic-seo-skill/seo-verifier"><img src="https://agentmods.dev/badge/agents/bhanunamikaze/agentic-seo-skill/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/bhanunamikaze/agentic-seo-skill/seo-verifier"><img src="https://agentmods.dev/badge/agents/bhanunamikaze/agentic-seo-skill/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 | $0.00013 | $0.00118 |
| Sonnet 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 9d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- seo-verifier — 100% identical, 0 lines differ
- seo-verifier — 100% identical, 0 lines differ
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.
- 9d ago First seen · 38 lines · 25 tokens per session scan A 6b44038fa513
seo-verifier is an agent published in the GitHub repository Bhanunamikaze/Agentic-SEO-Skill (892 stars, last pushed 1mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
sdd-architect
Specialized SDD Subagent for Phase 1 (Discovery) & Phase 2 (Spec Generation). Asks 3-5 sharp architectural questions using askquestion UI tool, drafts EARS requirements, creates Mermaid design diagrams, and generates uncapped A-C-E task lists.
sdd-executor
Specialized SDD Subagent for Phase 3 (Sequential Task Execution). Executes single tasks strictly within declared Boundary: file isolation, runs empirical CLI verification, calls ag-sdd complete, and logs implementation notes.
sdd-reviewer
Specialized SDD Subagent for Phase 4 (Quality Signoff). Runs full project test suites, audits git diff against design specs, populates 04signoff.md, and presents final quality assurance logs.
seo-flow
FLOW framework prompt analyst. Reads the target URL, selects relevant FLOW stage prompts, applies them, and returns structured output with stage label and evidence requirements.
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.