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 commands/brainbytes-dev/everything-claude-marketing/seo-auditgit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketingWrote 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/brainbytes-dev/everything-claude-marketing/seo-audit)<a href="https://agentmods.dev/commands/brainbytes-dev/everything-claude-marketing/seo-audit"><img src="https://agentmods.dev/badge/commands/brainbytes-dev/everything-claude-marketing/seo-audit.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 | $0.00023 | $0.01093 |
| Opus 5 | $0.00012 | $0.00547 |
| Sonnet 5 | $0.00005 | $0.00219 |
| Haiku 4.5 | $0.00002 | $0.00109 |
Grade A, and why
seo-audit 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/seo-audit
Run a comprehensive SEO analysis on your content, individual pages, or overall site structure. Get actionable recommendations across technical SEO, on-page optimization, and content strategy.
What This Command Does
The /seo-audit command evaluates your content or site against current SEO best practices and produces a prioritized list of improvements. It covers three pillars: technical health, on-page optimization, and content quality. Each finding comes with a severity level, specific fix instructions, and expected impact.
The command delegates to the seo-analyst agent, which applies search engine guidelines, ranking factor analysis, and content optimization frameworks to produce thorough, actionable audits.
When to Use
- You have a blog post or article and want to improve its search ranking potential
- You are publishing new content and want to optimize it before going live
- You need to audit a landing page for SEO fundamentals
- You want to evaluate your site's content structure and internal linking
- You are investigating a drop in organic traffic or rankings
- You need keyword optimization recommendations for existing content
- You want to assess content gaps relative to competitors
How It Works
- Content Analysis — Evaluates the provided content for keyword targeting, relevance, depth, and search intent alignment
- On-Page Assessment — Reviews title tags, meta descriptions, headings, URL structure, image alt text, and internal links
- Technical Review — Checks for crawlability issues, page speed signals, mobile-friendliness indicators, and structured data opportunities
- Keyword Evaluation — Analyzes keyword usage, density, semantic variations, and related terms coverage
- Competitive Context — Compares content depth and coverage against what typically ranks for target queries
- Recommendations — Produces a prioritized action list with effort vs. impact ratings
Example Usage
Input:
/seo-audit analyze our blog post about email marketing best practices
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 · 111 lines · 23 tokens per session scan A 3df592d22ae0
seo-audit is a command published in the GitHub repository brainbytes-dev/everything-claude-marketing (5 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 1,093 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.