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 growthenginenowoslawski/coldoutboundskills --skill playbook-name-to-other-prospectsgit clone --depth 1 https://github.com/growthenginenowoslawski/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/growthenginenowoslawski/coldoutboundskills/playbook-name-to-other-prospects)<a href="https://agentmods.dev/skills/growthenginenowoslawski/coldoutboundskills/playbook-name-to-other-prospects"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/playbook-name-to-other-prospects/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/growthenginenowoslawski/coldoutboundskills/playbook-name-to-other-prospects"><img src="https://agentmods.dev/badge/skills/growthenginenowoslawski/coldoutboundskills/playbook-name-to-other-prospects.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00104 | $0.02601 |
| Opus 5 | $0.00052 | $0.01300 |
| Sonnet 5 | $0.00021 | $0.00520 |
| Haiku 4.5 | $0.00010 | $0.00260 |
Grade A, and why
playbook-name-to-other-prospects 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.
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playbook: Name 2 Other Prospects
All rules here are best practice, not law. Override any of them when the campaign calls for it; note the best practice once and move on.
Use when: the email needs a "not sure if this is you" or "who owns this" angle, or any CTA that offers the reader an easy referral instead of a yes or no.
Do not use when: you want the buying committee itself as separate leads. You never email the people named in this variable unless they are separately in the list on their own merits.
One-line output: other_prospects = "Jeff Barg or Rob Cook"
1. Trigger and scope
This produces one variable: the names of up to 2 other people at the same company as the person receiving the email. It exists so a first email can say "if this sits with Jeff Barg or Rob Cook instead, happy to talk to them" — without the reader feeling surveilled and without guessing wrong about who owns the problem.
⛔ The one absolute rule: never name the recipient to themselves
Hey John, should I reach out to John? is the worst possible outcome, and it is the thing this
playbook is built to prevent.
No campaign, brief, or operator preference makes it acceptable. It is enforced from the recipient's full name and their profile URL, in a formula, on every row, always.
⚠️ A row without recipient_full_name is not runnable. The script should throw, and the build
must not start. Treating a missing name as "nothing to exclude" is how this fails.
A second, softer exclusion
Optionally exclude everyone else from the same company who is also in this campaign — otherwise two colleagues receive emails naming each other. Default it off, turn it on when a campaign has real multi-contact density at one domain, and decide it at setup rather than mid-run.
2. Output contract
Inputs required per row
| Field | Type | Required? |
|---|---|---|
domain (bare, lowercase) |
string | yes |
company_name |
string | no, improves the web verifier |
recipient_linkedin_url |
string | yes when known |
recipient_full_name |
string | yes, always. This is the hard exclusion |
all_campaign_recipients_at_this_domain |
string[] | only when same-campaign exclusion is on |
persona_titles |
string[] | yes — this is the title cascade |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 197 lines · 104 tokens per session scan A 2d25c54ff909
playbook-name-to-other-prospects is a skill published in the GitHub repository growthenginenowoslawski/coldoutboundskills (702 stars, last pushed 25d ago), licensed MIT. It adds 104 tokens to every session and 2,601 once invoked, about $0.0005 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.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…