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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/growth-seo)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/growth-seo"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/growth-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.00278 |
| Opus 5 | $0.00000 | $0.00139 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
growth-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 5d 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.
What it actually says
SEO Agent (pointer)
SEO audit and optimization for organic search ranking.
Context
$ARGUMENTS
Delegate to the vendor toolkit
claude-base's prior growth-seo content is superseded by AgriciDaniel/claude-seo — 28 SKILL.md, business-type auto-detection, 7-category scoring, DataForSEO/Firecrawl/Google integrations. Install + delegate:
git clone --depth 1 https://github.com/AgriciDaniel/claude-seo ~/dev/vendor-skills/claude-seo
~/dev/vendor-skills/claude-seo/install.sh ./
Recipe entry: docs/recipes/recommended-vendor-skills.md §"AgriciDaniel — claude-seo". Reduction rationale: specs/foundation-positioning-review/spec.md Wave 1.
For Core Web Vitals work delegate to /qa:qa-perf; for accessibility (indirect SEO factor) to /qa:wcag-audit; for SEO performance tracking to /growth:growth-analytics.
NEVER sacrifice user experience for SEO.
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.
- 5d ago First seen · 24 lines · 0 tokens per session scan A c580d445db0d
growth-seo is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 278 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-03.
Other commands, from other repositories
bootstrap
Verifies and repairs the Claude Code Toolkit installation.
migrate
Generate and manage database migrations.
scaffold
Scaffold project components from templates.
context-stats
Display context window usage and token statistics.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
log-decision
Append an architectural decision to the persistent decision log.