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-offer)<a href="https://agentmods.dev/commands/antonioblago/claude-code-seo-starter/visibly-seo-offer"><img src="https://agentmods.dev/badge/commands/antonioblago/claude-code-seo-starter/visibly-seo-offer/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-offer"><img src="https://agentmods.dev/badge/commands/antonioblago/claude-code-seo-starter/visibly-seo-offer.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.00011 | $0.00465 |
| Opus 5.5 | $0.00004 | $0.00186 |
| Sonnet 5.5 | $0.00002 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
visibly-seo-offer 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 3 — Writing an Offer (see docs/workflows.md) for client $ARGUMENTS.
Read first (do not skip)
Before drafting, load all client materials from ./clients/$ARGUMENTS/:
- Keyword files (Excel)
- Existing audits (PDF — extract text first)
- Call transcripts / email threads / previous offers
- Status-Quo and Potential outputs (must exist — otherwise run
/visibly-seo-status-quoand/visibly-seo-potentialfirst)
Client context to surface
- Budget constraints
- Internal resources (team size, agencies, in-house digital team)
- Decision makers & approval process
- Existing tools (CRM, ticketing, analytics)
- Pain points and goals from prior conversations
Structure
Fill in the skeleton at templates/offer-template.md —
don't invent a layout. It already has the phases, pricing table, ROI, terms and CTA:
- Phase 0: Setup & data review — explicitly recognise existing work (don't duplicate)
- Phase 1: Audit (SEO + optional SEA assessment)
- Phase 2: Monthly strategic accompaniment + enablement
- Phase 3: Optional advanced module (e.g. a signature methodology)
For each phase: scope, deliverables, timeline, investment.
Management-ready elements (all present in the template):
- Executive Summary (English if HQ is international)
- High-level milestone plan (quarterly)
- KPQ / KPI framework
- ROI section referencing the Potential-Analysis numbers
- Commercial terms (validity, payment, notice), assumptions & scope boundaries, and a clear next-step CTA
Output
Save to ./clients/$ARGUMENTS/YYYY-MM-DD_Offer/:
offer_<client>_<YYYY-MM-DD>.md(source — copy fromtemplates/offer-template.md)- Then run
/visibly-seo-pdf-buildto produce the brand-compliant PDF.
Pull your contact / bank / legal block from your own private notes — keep them out of this repo.
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 · 52 lines · 11 tokens per session scan A 02f3d16713cc
visibly-seo-offer is a command published in the GitHub repository AntonioBlago/claude-code-seo-starter (3 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 465 once invoked, about $0.0000 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.