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 skills add AlexisMarasigan/coldoutboundskills --skill prospeo-full-exportgit clone --depth 1 https://github.com/AlexisMarasigan/coldoutboundskillsWrote 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/alexismarasigan/coldoutboundskills/prospeo-full-export)<a href="https://agentmods.dev/skills/alexismarasigan/coldoutboundskills/prospeo-full-export"><img src="https://agentmods.dev/badge/skills/alexismarasigan/coldoutboundskills/prospeo-full-export/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/skills/alexismarasigan/coldoutboundskills/prospeo-full-export"><img src="https://agentmods.dev/badge/skills/alexismarasigan/coldoutboundskills/prospeo-full-export.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.00087 | $0.05211 |
| Opus 5 | $0.00044 | $0.02606 |
| Sonnet 5 | $0.00017 | $0.01042 |
| Haiku 4.5 | $0.00009 | $0.00521 |
Grade B, and why
prospeo-full-export scanned grade B with 1 finding 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 11d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
const response = await fetch('https://api.prospeo.io/search-person', { method: 'POST', This is a copy
100% identical to prospeo-full-export — 0 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 — 546 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prospeo Full Search Export
Extract your entire Prospeo people search to a CSV file. Build your search in Prospeo's UI, then let Claude pull every single result via the API — even if the search has more than 25,000 results.
Required step: Qualify with /icp-prompt-builder (do not skip)
Before exporting more than 500 contacts, run Prospeo on a 50-contact sample, then invoke /icp-prompt-builder to tune a qualification prompt in 3-5 rounds of 10 (with your approval each round). Apply the tuned prompt to the full export to filter out bad fits.
Why required: email enrichment downstream costs $0.05-$0.15 per person. A 25K export that's 40% wrong-fit wastes $500-$1,500 on email-finding that goes nowhere. The ICP prompt builder takes 10-15 min and saves that cost 40-70% of the time.
Safe skip: only if your Prospeo filter is already extremely tight (e.g., 5 exact titles + 1 industry + narrow headcount) AND you've run the same filter successfully before. Even then, run /icp-prompt-builder on 10 samples as a sanity check — it's nearly free to confirm.
What This Does
- You build a search in Prospeo's web UI (filters for title, location, industry, company size, etc.)
- You tell Claude what filters you used
- Claude translates those filters into Prospeo API calls
- Claude paginates through every page of results and exports to CSV
- For large US searches (25K+), Claude automatically splits by state to get everything
Setup (First Time Only)
Step 1: Create a Prospeo Account
- Go to prospeo.io and sign up
- Choose a plan that includes the Search Person API (most paid plans do)
- Each API request that returns results costs 1 credit and returns 25 contacts
Step 2: Get Your API Key
- Log into Prospeo
- Go to Settings > API (or visit prospeo.io/app/settings/api)
- Copy your API key
Step 3: Set Your API Key
Set it as an environment variable so Claude can use it:
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.
- 11d ago First seen · 546 lines · 87 tokens per session scan B 5a8e58b924e4
prospeo-full-export is a skill published in the GitHub repository AlexisMarasigan/coldoutboundskills (4 stars, last pushed 4mo ago), licensed MIT. It adds 87 tokens to every session and 5,211 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (sends data to an external url). It is 100% identical to prospeo-full-export, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…