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/commands/fatihkan/badi/seo)<a href="https://agentmods.dev/commands/fatihkan/badi/seo"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/seo.svg" alt="Measured on agentmods" 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.00000 | $0.00852 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
seo 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO audit command. Website SEO analysis, meta tag checks, sitemap validation, and speed assessment.
Required Tools
- Bash (badi seo commands)
Procedure
Step 1: Define the Scope
Ask the user: "Which analysis shall we run?"
- Full audit — 20+ checks (recommended starting point)
- Meta tags — OG, Twitter Card detail
- Sitemap + robots.txt — Crawlability
- Speed + resources — Performance starter
Step 2: SEO Audit (Default)
badi seo audit [url]
What is checked:
- Title, Description, OG tags, Twitter Card
- H1 structure (must be single)
- Image alt tags
- Canonical URL, Viewport, lang, charset
- HTTPS, Schema.org, robots meta
- Word count, link analysis
An SEO score of 0-100 is given.
Step 3: Detailed Analyses
badi seo meta [url] # Meta tag analysis (missing detection)
badi seo sitemap [url] # robots.txt + sitemap.xml
badi seo speed [url] # TTFB + HTML size + compression
Step 4: Improvement Suggestions
If the score < 80, based on the findings:
- Title missing/long: 30-60 character suggestion
- No description: 120-160 character example
- H1 problem: page structure suggestion
- Missing image alts: combined WCAG + SEO benefit
- No canonical: duplicate-content risk
- No Schema.org: structured-data opportunity
Step 5: Lighthouse Deep Analysis
For deeper metrics:
badi lighthouse [url]
Core Web Vitals + Performance + Accessibility + Best Practices + SEO score.
Step 6: AI Search Optimization (GEO/AEO)
Per Google's 2026 guidance, optimizing for AI features (AI Overviews, AI Mode) IS SEO — they pull from the same Search index via retrieval + query fan-out, so there is no separate "AI index" to target and indexability is AI visibility. Verify live (this space moves fast), but the durable levers:
- No special files or schema for Google AI — Google explicitly ignores
llms.txtand requires no AI-specific schema or content "chunking." Don't waste effort there; foundational SEO + original, non-commodity content is the lever. (Other engines may readllms.txt, but none have committed to acting on it — don't rely on it.) - Lead with the answer + evidence — front-load the substantive answer and original data/statistics/citable claims; studies show AI engines preferentially quote early, evidence-rich passages.
- Earn off-site brand mentions — authentic third-party mentions/press correlate with AI citation more than backlinks; build distribution, not just links.
- Structured-data hygiene — schema still aids eligibility, but FAQ rich results were deprecated (2026); audit and remove inert FAQ markup.
- Measure AI visibility, not just clicks — clicks fall when AI answers appear while brand exposure rises; track the Search Console Gen AI (AI feature) impression report + branded-search volume. Don't block
Google-Extendedexpecting to control AI Overviews — it governs Gemini Apps, not Search AI features. - Preferred Sources — if you run a publisher/brand, add Google's Preferred Sources button (the official user-level mechanism to surface in Top Stories / AI features).
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 · 84 lines · 0 tokens per session scan A 9c7ae9c6c42c
seo is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 852 tokens. 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-09-06.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
qa
Systematic QA testing of a web application — diff-aware, tiered, with fix-and-verify loop.
review-pr
Perform a comprehensive code review of a pull request.
security-audit
Comprehensive security audit with scored posture assessment.