upgradeseo: Skill for Claude Code

.agents/skills/link-prospecting/SKILL.md

link-prospecting is a skill for Claude Code, Codex from upgrade-ventures/upgradeseo. It costs 23 tokens per session (994 once invoked), scanned A, a copy of link-prospecting, MIT.

An SEO research workflow for finding websites, pages, and authors that might link to your content. SEO, or search engine optimisation, is the work of improving how pages appear in search results.

In plain words
What is it for?
Finding ranking articles, resource pages, publishers, competitors’ backlinks, suitable domains, and possible contact paths for outreach.
Why use it?
It removes the need to search for link opportunities and contact details by hand. It also helps assess whether potential sources are relevant.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is upgrade-ventures/upgradeseo's own configuration. It tells Claude Code and Codex how to work on upgradeseo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything upgradeseo configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/upgrade-ventures/upgradeseo/main/.agents/skills/link-prospecting/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/upgrade-ventures/upgradeseo

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for link-prospecting

README.md
[![agentmods](https://agentmods.dev/badge/skills/upgrade-ventures/upgradeseo/link-prospecting.svg)](https://agentmods.dev/skills/upgrade-ventures/upgradeseo/link-prospecting)
Your own site
<a href="https://agentmods.dev/skills/upgrade-ventures/upgradeseo/link-prospecting"><img src="https://agentmods.dev/badge/skills/upgrade-ventures/upgradeseo/link-prospecting.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 994 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00994
Opus 5 $0.00012 $0.00497
Sonnet 5 $0.00005 $0.00199
Haiku 4.5 $0.00002 $0.00099

Measured 7d ago against content hash 87e5394f64be, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

link-prospecting 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.

Origin

This is a copy

95% identical to link-prospecting — 19 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.

.agents/skills/link-prospecting/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Goal

Find realistic pages, sites, and authors that might reference the user's page, product, study, guide, or tool. Use UpgradeSEO for prospect discovery, then use available web/search/browser tools for contact discovery.

Required inputs

  • projectId
  • User domain or target URL
  • Linkable asset, page, product, study, tool, or topic
  • Optional competitors
  • Optional market/location/language

UpgradeSEO MCP tools

  • get_serp_results: find ranking articles, listicles, resource pages, comparisons, and topical publishers.
  • get_backlinks_overview: inspect competitor domain or page backlink/referring-domain patterns.
  • get_domain_overview: qualify important prospect domains.
  • get_ranked_keywords: understand what a prospect or competitor ranks for when topical fit matters.
  • search_local_businesses and get_local_serp_results: use for local SEO link prospecting when nearby businesses, local competitors, or Maps/category signals can reveal partnership targets.
  • research_keywords: expand prospecting queries.

Contact discovery tools

After UpgradeSEO identifies good prospects, use available non-UpgradeSEO browsing or search tools for public contact discovery. Depending on the client, this may be web search, page fetches, browser automation, or a search API.

Look for:

  • Author byline pages
  • Contact pages
  • Editorial guidelines
  • About/team pages
  • LinkedIn, X, Bluesky, or other professional profiles
  • Newsletter or publication masthead pages
  • Public email addresses in page HTML or visible page text
  • Structured data such as Person, Organization, sameAs, or email

Only record contact details that were actually found. Include the source URL for any email, profile, or contact form.

Prospecting query patterns

Build queries from the asset/topic:

  • <topic> resources
  • best <category> tools
  • <competitor> alternatives
  • <topic> statistics
  • <topic> guide
  • <topic> examples
  • <topic> templates
  • <topic> software
  • <topic> for <audience>

Read the full file on GitHub · 108 lines

Changes

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.

  1. 7d ago First seen · 108 lines · 23 tokens per session scan A 87e5394f64be

Subscribe to this mod's changes

link-prospecting is a skill published in the GitHub repository upgrade-ventures/upgradeseo (1 stars, last pushed 20d ago), licensed MIT. It adds 23 tokens to every session and 994 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to link-prospecting, differing in 19 lines, and is treated as a copy.

Related

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.

osodevops/intelligence-layer-skills · 66 tokens

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…

osodevops/intelligence-layer-skills · 70 tokens

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.

osodevops/intelligence-layer-skills · 74 tokens

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…

osodevops/intelligence-layer-skills · 71 tokens

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…

osodevops/intelligence-layer-skills · 73 tokens

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.

osodevops/intelligence-layer-skills · 71 tokens