geo-prospect

geo-prospect is a skill for Claude Code from zubair-trabzada/geo-seo-claude. It costs 87 tokens per session (1,730 once invoked), scanned A, original, MIT.

A small customer-tracking system for GEO agencies. GEO, or generative engine optimization, means improving how websites appear in answers from AI search tools.

In plain words
What is it for?
Use it to create and review prospects, run and save GEO audits, add notes, move deals through the sales pipeline, and summarize expected revenue.
Why use it?
It keeps leads, clients, notes, audits, deal values, and sales stages in one persistent JSON file instead of scattered records.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to create and review prospects, run and save GEO audits, add notes, move deals through the sales pipeline, and summarize expected revenue.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zubair-trabzada/geo-seo-claude/geo-prospect
About the project

geo-seo-claude is a Claude Code skill for improving how websites appear in AI-powered search while retaining traditional search-engine optimization. It is used by marketers and website practitioners for analysis such as citation scoring, crawler review, authority assessment, structured data, and platform-specific recommendations. The catalogue entries are skills and agents that carry out this optimization workflow.

zubair-trabzada/geo-seo-claude · 10,540 stars · on GitHub · skool.com

Install

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.

Any agent
npx skills add zubair-trabzada/geo-seo-claude --skill geo-prospect
Clone the repo
git clone --depth 1 https://github.com/zubair-trabzada/geo-seo-claude

Made for: Claude Code.

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 geo-prospect

README.md
[![agentmods](https://agentmods.dev/badge/skills/zubair-trabzada/geo-seo-claude/geo-prospect/github.svg)](https://agentmods.dev/skills/zubair-trabzada/geo-seo-claude/geo-prospect)
Your own site
<a href="https://agentmods.dev/skills/zubair-trabzada/geo-seo-claude/geo-prospect"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/geo-seo-claude/geo-prospect/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.

agentmods 80×15 button for geo-prospect

Your own site · 80×15
<a href="https://agentmods.dev/skills/zubair-trabzada/geo-seo-claude/geo-prospect"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/geo-seo-claude/geo-prospect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,730 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. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 18 Mar 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 78
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Rogue Agent · line 173
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found 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.00087 $0.01730
Opus 5 $0.00044 $0.00865
Sonnet 5 $0.00017 $0.00346
Haiku 4.5 $0.00009 $0.00173

Measured 13d ago against content hash 825f05d74dc0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

geo-prospect 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 13d 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

Copies of this mod

3 near-identical copies found in the catalogue:

skills/geo-prospect/SKILL.md · 194 lines

How it starts

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

GEO Prospect Manager

Purpose

Manage GEO agency prospects and clients through the full sales lifecycle. All data is stored in ~/.geo-prospects/prospects.json (persistent across sessions).


Commands

Command What It Does
/geo prospect new <domain> Create new prospect (interactive prompts)
/geo prospect list Show all prospects with pipeline status
/geo prospect list <status> Filter: lead, qualified, proposal, won, lost
/geo prospect show <id-or-domain> Full prospect detail with history
/geo prospect audit <id-or-domain> Run quick GEO audit and save to prospect record
/geo prospect note <id-or-domain> "<text>" Add interaction note with timestamp
/geo prospect status <id-or-domain> <new-status> Move through pipeline
/geo prospect won <id-or-domain> <monthly-value> Mark as won, set contract value
/geo prospect lost <id-or-domain> "<reason>" Mark as lost with reason
/geo prospect pipeline Visual pipeline summary with revenue forecast

Data Structure

Each prospect is stored as a JSON record:

{
  "id": "PRO-001",
  "company": "Electron Srl",
  "domain": "electron-srl.com",
  "contact_email": "[email protected]",
  "contact_name": "",
  "industry": "Educational Equipment Manufacturing",
  "country": "Italy",
  "status": "qualified",
  "geo_score": 32,
  "audit_date": "2026-03-12",
  "audit_file": "~/.geo-prospects/audits/electron-srl.com-2026-03-12.md",
  "proposal_file": "~/.geo-prospects/proposals/electron-srl.com-proposal.md",
  "monthly_value": 0,
  "contract_start": null,
  "contract_months": 0,
  "notes": [
    {
      "date": "2026-03-12",
      "text": "Initial GEO quick scan. Score 32/100 - Critical tier. Strong candidate for GEO services."
    }
  ],
  "created_at": "2026-03-12",
  "updated_at": "2026-03-12"
}

Orchestration Instructions

/geo prospect new <domain>

  1. Check if ~/.geo-prospects/prospects.json exists, create if not (empty array)
  2. Auto-detect company name from domain (e.g., electron-srl.comElectron Srl)
  3. Assign next sequential ID: PRO-001, PRO-002, etc.
  4. Ask user for:
    • Contact name (optional)
    • Contact email
    • Monthly contract value estimate (optional)
  5. Set status to lead
  6. Save to JSON file
  7. Suggest next step: "Run /geo prospect audit electron-srl.com to score this prospect"

Read the full file on GitHub · 194 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. 13d ago First seen · 194 lines · 87 tokens per session scan A 825f05d74dc0

Subscribe to this mod's changes

geo-prospect is a skill published in the GitHub repository zubair-trabzada/geo-seo-claude (10,540 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 1,730 once invoked, about $0.0004 per session on Opus 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-30.

Related

Other skills, from other repositories

geo-prospect

CRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit history, notes, deal values, and generate pipeline summaries. Use when user says "prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi…

asale-ai/seo-geo-skill · 87 tokens

geo-prospect

CRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit history, notes, deal values, and generate pipeline summaries. Use when user says "prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi…

techhorizonlabs/thl-open · 87 tokens

client-relationship-manager

Lightweight AI-native CRM for solopreneurs and freelancers. Track clients, relationships, follow-ups, deal stages, and interaction history in plain text files — no SaaS subscription required. Use when managing client relationships, preparing for meetings, tracking follow-ups, or reviewing pipeline status.

theagentledger/agent-skills · 62 tokens

afrexai-lead-hunter

Enterprise-grade B2B lead generation, enrichment, scoring, and outreach sequencing for AI agents. Find ideal prospects, enrich with verified data, score against your ICP, and generate personalized outreach — all autonomously.

LeoYeAI/openclaw-master-skills · 50 tokens

sales-expert

Build comprehensive sales technology solutions including CRM implementation, pipeline management, sales forecasting, and performance analytics. Use when the user mentions CRM, sales pipelines, lead qualification, opportunity tracking, sales forecasting, quotas or territories, or sales automation.

personamanagmentlayer/pcl · 50 tokens

sales-director

The Chief Revenue Officer (CRO) — manages ALL sales activities across 1ai-affiliate and 1ai-career. Delegates to lead generation, pipeline management, closing, and customer success. Has memory via 1ai-hub brain, follows 1ai-rules, and coordinates with Marketing Director for leads and Content Director for sales…

oyi77/1ai-skills · 103 tokens