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/AntonioBlago/claude-code-seo-starterWrote 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/antonioblago/claude-code-seo-starter/visibly-seo-potential)<a href="https://agentmods.dev/commands/antonioblago/claude-code-seo-starter/visibly-seo-potential"><img src="https://agentmods.dev/badge/commands/antonioblago/claude-code-seo-starter/visibly-seo-potential/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/commands/antonioblago/claude-code-seo-starter/visibly-seo-potential"><img src="https://agentmods.dev/badge/commands/antonioblago/claude-code-seo-starter/visibly-seo-potential.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.00014 | $0.00588 |
| Opus 5 | $0.00007 | $0.00294 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
visibly-seo-potential 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.
What it actually says
Run Workflow 2 — Potential Analysis (see docs/workflows.md) for client $ARGUMENTS.
Preconditions
- Status-Quo output must exist under
./clients/$ARGUMENTS/. If it does not, stop and tell the user to run/visibly-seo-status-quo $ARGUMENTSfirst.
Steps
- Load the Status-Quo table (xlsx):
python -c "import pandas as pd; df = pd.read_excel('clients/$ARGUMENTS/.../status_quo.xlsx'); print(df.columns.tolist())" - Apply the empirical CTR model from
docs/ctr-model.md. Pos 1 ≈ 5.59 %, Pos 2 ≈ 3.15 %, Pos 3 ≈ 2.37 % … (real-world, not idealised). Never use the old textbook curve (Pos 1 = 28 %). - Set realistic 12-month target positions based on current position + search volume:
- Currently > 100, SV > 10k → target Pos 15
- Currently > 100, SV 5-10k → target Pos 12
- Currently > 100, SV 1-5k → target Pos 8
- Currently > 100, SV < 1k → target Pos 5
- Already ranking → improve 1-10 positions depending on current
- Compute Δ clicks per keyword and aggregate by cluster/theme.
- B2B lead calc: contact rate 1.5 % / 2.5 % / 3.5 %, close rate 10-20 %, industry-specific deal value.
- SEA equivalence:
Δclicks × avg CPC→ ad-spend saved. - ROI: investment vs. (SEA value + lead value).
Output
Fill in the skeleton at templates/potential-template.md —
don't invent a layout. It already has the method/assumptions block, the target-position
matrix, the per-keyword delta table, the cluster rollup, Top-20-by-delta, the three-scenario
value table, and the ROI section.
Save to ./clients/$ARGUMENTS/YYYY-MM-DD_Potential/:
potential_<YYYY-MM-DD>.md(summary — copy fromtemplates/potential-template.md)potential_<YYYY-MM-DD>.xlsx(per-keyword Δ + cluster rollup — all rows)roi_scenarios.md(conservative / realistic / optimistic)
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 · 45 lines · 14 tokens per session scan A 59494344b68b
visibly-seo-potential is a command published in the GitHub repository AntonioBlago/claude-code-seo-starter (3 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 588 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
seo-geo
SEO/GEO end-to-end along the SITE loop: survey demand and competitors, implement content, tune quality/tech/on-page, and evaluate authority/rankings/reports/memory (--phase survey|implement|tune|evaluate). Not sure? Use /aaron-marketing:auto.
ad
Run a paid-ads (ROAS) workflow: audience segments, account structure, ad creative, experiment design, pre-launch signal QA + the account-audit gate, measurement, and attribution. Not sure? Use /aaron-marketing:auto.
launch
Run a product-launch (RAMP) workflow: positioning and launch tiering, window/early-access design, message house and asset kits, the launch-readiness gate with a T-1 go/no-go, launch-day execution, and the post-launch prove loop. Not sure? Use /aaron-marketing:auto.
wp-seed
Seed WordPress content from demo HTML — parses sections, creates pages, imports media, populates ACF fields, builds menus, supports bilingual content.
wp-audit
Comprehensive audit — security, SEO, accessibility, performance, best practices.
wp-tailwindify
Convert an HTML/CSS demo to Tailwind-native HTML — preserves section delimiters, maps colors to @theme variables.