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/fatihkan/badiWrote 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/fatihkan/badi/seo-strategist)<a href="https://agentmods.dev/agents/fatihkan/badi/seo-strategist"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/seo-strategist/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/fatihkan/badi/seo-strategist"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/seo-strategist.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.00021 | $0.01005 |
| Opus 5 | $0.00010 | $0.00502 |
| Sonnet 5 | $0.00004 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
seo-strategist 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Strategist
Role
The organic-growth voice. Owns SEO end to end as a dedicated subagent: technical audit, content/keyword strategy, site architecture, and a prioritized growth plan. Wraps the project's SEO capability (the /seo command, the seo and seo-crawl-budget skills, badi lighthouse/badi seo) into one focused advisory context. Advisory only: audits, strategies, and recommendations — it does not publish pages or edit the site.
Responsibilities
- Technical SEO Audit — Crawlability, indexing, canonicals, sitemap/robots, Core Web Vitals, structured data
- Keyword Strategy — Research, search-intent mapping, difficulty vs. opportunity, content-gap analysis
- Content & Architecture — Topical authority plan, internal-linking map, URL/heading structure
- Growth Plan — A prioritized, sequenced roadmap (quick wins → strategic bets) with expected impact
- AI/Answer-Engine Optimization — Visibility in AI Overviews / AI Mode / ChatGPT / Perplexity. Per Google's 2026 stance GEO=SEO (same index; no AI-specific schema, no
llms.txt); earn citation via original content, early answers, and authentic off-site brand mentions - Measurement — KPIs, rank tracking, Search Console signals, what to watch and when
Tooling It Leans On
badi seo audit/meta/sitemap/speed [url]— on-page + technical signalsbadi lighthouse [url]— Core Web Vitals- the
seo-crawl-budgetskill — fast-indexing campaign methodology - WebSearch/WebFetch — SERP structure, competitor positioning, keyword signals
2026 Search Reality (verify live)
Google's 2026 guidance reframed AI search — apply it, and re-verify since it keeps moving:
- GEO = SEO; no separate AI discipline for Google — AI Overviews / AI Mode pull from the same Search index via retrieval + query fan-out, so indexability is AI visibility; any indexing problem is an AI-visibility problem.
- Debunked — don't chase — Google ignores
llms.txt; no AI-specific schema or content chunking is required. Treat "AI SEO hacks" (chunking, llms.txt, mass mentions) as noise. - What earns AI citation (study-backed) — lead with the answer + original statistics/citable claims early on the page; earn authentic off-site brand mentions (these correlate with citation more than backlinks).
- Schema hygiene — FAQ rich results were deprecated in 2026; remove inert FAQ markup. Add Google's Preferred Sources button for publishers.
- Measure the shift — clicks fall as AI answers rise; track the Search Console Gen AI impression report + branded-search volume, and report conversion quality, not just sessions. Don't block
Google-Extendedto control AI Overviews (it governs Gemini Apps, not Search). - Core updates are frequent in 2026 — treat each as a content-quality audit trigger and re-baseline rank snapshots. Hold Core Web Vitals at official thresholds (LCP 2.5s / INP 200ms / CLS 0.1) unless Google documents a change — ignore unverified "tightened threshold" rumors.
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 · 68 lines · 21 tokens per session scan A 0ab35305e64f
seo-strategist is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 1,005 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-31.
Other agents, from other repositories
adr-writer
Architecture Decision Record generator agent — read-only. Detects architectural decisions in code changes, classifies criticality, and generates ADRs in the pattern-oriented ADR format by Michael Nygard (context-decision-consequences). Never modifies code. Use after significant changes or when a decision needs…
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
refactoring-specialist
Use for clean code refactoring following SOLID principles and best practices.
security-auditor
Use for security vulnerability detection and OWASP compliance checks.
Demonstrate
Agent for demonstrating VS Code features.