Borrowing it
Nothing to install: this file belongs to upgrade-ventures/upgradeseo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/upgrade-ventures/upgradeseo/main/.agents/skills/seo-project-setup/SKILL.mdgit clone --depth 1 https://github.com/upgrade-ventures/upgradeseoWrote 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/skills/upgrade-ventures/upgradeseo/seo-project-setup)<a href="https://agentmods.dev/skills/upgrade-ventures/upgradeseo/seo-project-setup"><img src="https://agentmods.dev/badge/skills/upgrade-ventures/upgradeseo/seo-project-setup.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.00033 | $0.01398 |
| Opus 5 | $0.00016 | $0.00699 |
| Sonnet 5 | $0.00007 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
seo-project-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 7d 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.
This is a copy
94% identical to seo-project-setup — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UpgradeSEO SEO Project Setup
Goal
Help the user set up a local SEO workspace for one website or SEO project. The folder is where the agent saves notes, goals, exports, briefs, reports, preferences, and project context over time. This is a workspace and context setup workflow, not a full audit.
Tone
Be friendly, practical, and structured. Ask questions in small batches. Explain why each item matters only when useful. Do not overwhelm a beginner with jargon.
Checklist
1. Pick a working folder
Suggest that the user choose or create a local folder for SEO work, for example:
~/SEO/<company-or-site>/~/Documents/SEO/<company-or-site>/- A repo or workspace folder if SEO work should live beside website/content files
Explain that keeping notes, exports, briefs, scraped pages, reports, and preferences in one folder helps the agent build context over time. Future SEO workflows can use that folder rather than starting from a blank conversation.
Recommended starter structure:
seo-workspace/
README.md
gsc/
keywords/
competitors/
content/
outreach/
reports/
Do not create folders unless the user asks. If file tools are available and the user asks, create a simple structure and a short README.md with the current goals, known sites, and user preferences for how the agent should approach SEO for this project.
2. Collect website scope
Ask for:
- Primary website/domain
- Additional domains or subdomains
- Important products, services, categories, or pages
- Target countries/languages
- Whether the site is new, established, migrating, or recovering from a drop
- CMS or publishing workflow, if relevant
3. Capture goals
Ask the user what they want from SEO:
- More qualified leads
- More signups/trials
- More ecommerce revenue
- More newsletter/audience growth
- More brand/category awareness
- Recovery from traffic loss
- Better ranking for specific pages
Ask for success metrics and timeframe. If goals are vague, help turn them into measurable goals such as "increase non-branded organic signups" or "rank top 10 for 20 buying-intent terms."
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.
- 7d ago First seen · 167 lines · 33 tokens per session scan A 6c77dd81e8e4
seo-project-setup is a skill published in the GitHub repository upgrade-ventures/upgradeseo (1 stars, last pushed 20d ago), licensed MIT. It adds 33 tokens to every session and 1,398 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to seo-project-setup, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
semrush-backlink-audit
Audit backlink profiles with the semrush CLI. Use when the user asks for backlink analysis, referring domains, authority score, anchor text, indexed linked pages, backlink competitors, link gaps, backlink history, toxic or suspicious link signals, or off-page SEO recommendations based on Semrush CLI backlink data.
semrush-cli-setup
Install, configure, validate, and troubleshoot the semrush CLI. Use when the user needs Semrush API auth, SEMRUSHAPIKEY or SEMRUSHOAUTHTOKEN setup, output/cache/rate-limit configuration, shell completions, API balance checks, structured error handling, or a prerequisite check before running other Semrush CLI skills.
semrush-competitor-research
Analyze SEO competitors, organic keywords, top pages, subdomains, and keyword gaps with the semrush CLI. Use when the user asks for competitor research, organic competitor discovery, content gaps, domain comparison, missing or untapped keywords, page-level SEO opportunities, or a competitive SEO audit using Semrush…
semrush-keyword-research
Research, expand, score, and prioritize SEO keywords with the semrush CLI. Use when the user asks for keyword research, search volume, CPC, difficulty, related keywords, broad-match keywords, question keywords, keyword clustering inputs, SERP domains for a query, or a prioritized keyword opportunity table powered by…
semrush-batch-workflows
Create, estimate, run, and adapt semrush CLI TOML batch recipes. Use when the user needs reusable Semrush CLI workflows, competitor audit recipes, keyword opportunity recipes, backlink audit recipes, paid-search recipes, traffic summary recipes, scheduled SEO data pulls, or API-unit estimates before multi-step Semrush…
semrush-local-seo
Manage and analyze local SEO data with semrush CLI v4 commands. Use when the user asks for Semrush local listings, local business location records, Google Maps or map-rank campaigns, map-rank keywords, heatmaps, local competitors, NAP/listing QA, or local SEO reporting through the Semrush CLI.