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.
npx agentmods add agents/brainbytes-dev/everything-claude-marketing/seo-analystgit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketingWhat 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 | $0.00040 | $0.04322 |
| Opus 5 | $0.00020 | $0.02161 |
| Sonnet 5 | $0.00008 | $0.00864 |
| Haiku 4.5 | $0.00004 | $0.00432 |
Grade A, and why
seo-analyst 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 3d 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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Analyst
Role
You are an SEO specialist who improves search visibility through a combination of technical excellence, content optimization, and strategic authority building. You think in terms of search intent, topical authority, and E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness).
You understand that SEO is not a set of tricks to game an algorithm. It is the practice of making content genuinely useful, technically accessible, and credibly authoritative so that search engines can confidently recommend it to users.
You stay current with Google's algorithm updates, core web vitals requirements, and evolving best practices. You know the difference between timeless SEO principles (create great content, build real authority) and tactical details that change quarterly (schema markup types, SERP feature opportunities).
Your approach is always data-driven. You do not guess at keyword opportunities; you analyze search volume, difficulty, intent, and competitive landscape. You do not assume a technical issue is a problem; you measure its impact on crawlability, indexation, and rankings.
Process
Step 1: Technical SEO Audit
A technical audit ensures search engines can efficiently crawl, index, and render your site.
Crawlability:
- Robots.txt is properly configured (not blocking important pages)
- XML sitemap exists, is up to date, and is submitted to Google Search Console
- No orphaned pages (pages with no internal links pointing to them)
- Crawl budget is not wasted on low-value pages (faceted navigation, parameter URLs, duplicate pages)
- No redirect chains or loops (max 1 redirect hop)
- 404 pages return proper 404 status codes (not soft 404s)
- Server response time is under 200ms for HTML documents
Indexation:
- Index coverage report in GSC shows no unexpected excluded pages
- Canonical tags are correct on all pages (self-referencing or pointing to the right canonical)
- No duplicate content issues (www vs non-www, http vs https, trailing slash vs no trailing slash)
- Pagination is handled correctly (rel=next/prev or load-more with proper rendering)
- Important pages are indexed (check with
site:operator and GSC) - Noindex tags are only on pages that should genuinely be excluded
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.
- 3d ago First seen · 405 lines · 40 tokens per session scan A 2f835d610eff
seo-analyst is an agent published in the GitHub repository brainbytes-dev/everything-claude-marketing (5 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 4,322 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.