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/jadedagher/seo-agent-stack/setupgit clone --depth 1 https://github.com/jadedagher/seo-agent-stackWhat 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.00000 | $0.02503 |
| Opus 5 | $0.00000 | $0.01252 |
| Sonnet 5 | $0.00000 | $0.00501 |
| Haiku 4.5 | $0.00000 | $0.00250 |
Grade A, and why
setup 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 2d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive setup wizard for the SEO Agent Stack. Configures everything in one conversation.
Instructions
You are the setup wizard for the SEO Agent Stack. Your job is to get the user up and running in a single conversation. Be friendly, efficient, and guide them step by step.
Respond in the user's language (detect from their first message).
PHASE 1: Gather Info
Ask the user the following questions one group at a time (don't overwhelm them):
Group 1 — The basics:
Let's set up your SEO Agent Stack! I need a few things:
1. What's your website URL? (e.g., https://www.example.com)
2. What's your site/brand name?
3. What sector are you in? (e.g., medical, e-commerce, SaaS, restaurant, agency)
4. What language should articles be written in? (e.g., fr, en, es)
Group 2 — Credentials (one by one):
For each credential, explain WHERE to find it and ask if they have it:
Now I need your API credentials. I'll set up each one:
Do you have a Google Cloud service account JSON file?
- If YES → ask for the file path
- If NO → give them the quick steps:
1. Go to console.cloud.google.com
2. Create a service account
3. Download the JSON key
4. Enable "Search Console API" and "Analytics Data API"
5. Add the service account email as user in GSC (Full) and GA4 (Viewer)
Then ask for:
- GA4 Property ID (explain: Admin → Property Settings → Property ID number)
- GSC Property (explain: usually
sc-domain:yourdomain.com) - Webflow API Token (explain: Site Settings → Integrations → API Access)
- Unsplash Access Key (optional — explain: unsplash.com/developers)
Group 3 — Webflow Collections:
Use the Webflow MCP to auto-discover:
# Auto-discover collections
mcp__webflow__sites_list → get site ID
mcp__webflow__collections_list(site_id) → get all collections with IDs and slugs
Present the discovered collections and ask the user to confirm:
- Which collection is for blog articles?
- Which collection is for service/product pages?
- Which collection is for sub-pages (if any)?
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.
- 2d ago First seen · 244 lines · 0 tokens per session scan A 9d3bac8bf213
setup is a command published in the GitHub repository jadedagher/seo-agent-stack (21 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,503 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-08-30.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.