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-status-quo)<a href="https://agentmods.dev/commands/antonioblago/claude-code-seo-starter/visibly-seo-status-quo"><img src="https://agentmods.dev/badge/commands/antonioblago/claude-code-seo-starter/visibly-seo-status-quo/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-status-quo"><img src="https://agentmods.dev/badge/commands/antonioblago/claude-code-seo-starter/visibly-seo-status-quo.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.00019 | $0.00501 |
| Opus 5.5 | $0.00008 | $0.00200 |
| Sonnet 5.5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
visibly-seo-status-quo 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 1mo 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 1 — SEO Status-Quo Analysis (see docs/workflows.md) for client $ARGUMENTS.
Inputs
- Client folder:
./clients/$ARGUMENTS/(create if missing) - Keyword files: look for
*.xlsx,*.csvin the client folder - GSC: via Visibly AI MCP (
list_projects→ match domain →query_search_console)
Steps
mcp__visiblyai__list_projects— find the project matching$ARGUMENTSmcp__visiblyai__get_google_connections— confirm GSC is wiredmcp__visiblyai__query_search_consolewith country filter,dimension=query,limit=500- Repeat with
dimension=pagefor underperforming URLs - Read the client keyword Excel/CSV (pandas):
python -c "import pandas as pd; print(pd.read_excel('clients/$ARGUMENTS/keywords.xlsx').head())" - Cross-reference target keywords against GSC (clicks, impressions, CTR, position)
- Classify: Brand / Generic / Competitor × Top3 / Page1 / Page2 / Weak / Not Ranking
- Flag Quick Wins: high impressions, CTR < 5 %
- Competitor benchmark (if competitors are known for this client)
Output
Fill in the skeleton at templates/status-quo-template.md —
don't invent a layout. It already has the visibility-at-a-glance counts, the classification
split, the cross-referenced keyword table, underperforming pages, quick wins, and the
competitor benchmark. Live-verified GSC values only.
Save to ./clients/$ARGUMENTS/YYYY-MM-DD_Status-Quo/:
status_quo_<YYYY-MM-DD>.md(summary — copy fromtemplates/status-quo-template.md)status_quo_<YYYY-MM-DD>.xlsx(full cross-referenced table — all rows)quick_wins.md(actionable list, specific lever per keyword)
Use today's date for the folder and filename.
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.
- 1mo ago First seen · 42 lines · 19 tokens per session scan A d7bfa1458506
visibly-seo-status-quo is a command published in the GitHub repository AntonioBlago/claude-code-seo-starter (3 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 501 once invoked, about $0.0001 per session on Opus 5.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
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-responsive-check
Responsive validation — screenshots at 9 viewports, checks for layout issues.
yt
Route to the YouTube Agent Matrix orchestrator — the full pre-production pipeline.
wp-cinematic-encode
Encode source videos for cinematic scroll-scrub (all-keyframe MP4) and mobile autoplay-loop (9:16 portrait crop). Thin wrapper over the kit's scripts/encode-keyframe.sh and scripts/encode-mobile-portrait.sh. Drops encoded files into /assets/videos/ and updates the matching ACF row if --scene=N is provided.
crew-workflow
Run a multi-persona workflow (strategy-review, content-pipeline, product-launch).
crm-contact
Add, update, or look up a contact in StudioMeyer CRM.