Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Ken-Technology/cold-email-skillsnpx agentmods add skills/ken-technology/cold-email-skills/cold-email-campaignWrote 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/ken-technology/cold-email-skills/cold-email-campaign)<a href="https://agentmods.dev/skills/ken-technology/cold-email-skills/cold-email-campaign"><img src="https://agentmods.dev/badge/skills/ken-technology/cold-email-skills/cold-email-campaign/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/ken-technology/cold-email-skills/cold-email-campaign"><img src="https://agentmods.dev/badge/skills/ken-technology/cold-email-skills/cold-email-campaign.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.00100 | $0.01461 |
| Opus 5 | $0.00050 | $0.00731 |
| Sonnet 5 | $0.00020 | $0.00292 |
| Haiku 4.5 | $0.00010 | $0.00146 |
Grade A, and why
cold-email-campaign 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 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.
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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Email Campaign
What this does
Run a full cold-email campaign as a files-only workflow: no account, no API keys, no platform push, no sending. You gather (or produce) client research, write a campaign plan (1 broad ICP + 1 offer + N segments), define portable search filters, qualification rules, and segmentation, then for every segment produce strategy, reviewed email copy, and AI personalization prompts. When the pipeline finishes, the workspace holds a ready-to-send sequence the user can load into their own list tool and sending platform.
Workspace
Create a campaign workspace at ./cold-email/{slug}/, where {slug} is a short lowercase hyphenated name for the client or campaign (for example acme-outbound or fintech-founders). Put all plan-level and segment-level files under that folder. Do not invent platform config files; the free workflow stops at markdown artifacts.
./cold-email/{slug}/
├── research.md
├── plan.md # H1 = campaign name; 1 ICP + 1 offer + N segments
├── search-strategy.md
├── qualification.md
├── segmentation.md
├── 0 - default/ # strategy.md, emails_v2.md, prompts.md
└── 1 - {segment}/
Layout rules:
plan.mdhas a single top-level# {Campaign Name}H1.- Always scaffold
0 - default/as the catch-all segment (broadest messaging for contacts that do not fit a numbered segment). - Numbered segments use
N - {segment-slug}/(for example1 - healthcare-saas/,2 - fintech-founders/). Create one folder per segment defined in the plan. - Each segment folder holds
strategy.md,emails.md(draft),emails_v2.md(reviewed), andprompts.md.
Pipeline
Run the steps below in order. Name each skill when you invoke it so the user can see progress. Write every artifact into the workspace before moving on.
1. Research
If research.md is missing and the user has not already provided enough context (notes, call transcripts, site copy, offer one-pager), run client-research (or ask them to paste notes, transcripts, or site text). Write or confirm research.md at the workspace root. Do not invent an ICP or offer.
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 · 99 lines · 100 tokens per session scan A df58a429ee4e
cold-email-campaign is a skill published in the GitHub repository Ken-Technology/cold-email-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 100 tokens to every session and 1,461 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-31.
Other skills, from other repositories
outbound-strategy
Build your own in-house cold email / outbound infrastructure instead of renting Smartlead, Instantly or Lemlist. Use when someone wants to set up self-hosted cold outreach: connecting their own SMTP/IMAP inboxes, sourcing and segmenting B2B leads, writing multi-step sequences, sending at scale with deliverability-safe…
cold-email-onboarding
First-run interactive setup for the cold-email skill pack. Walks the operator through brand-config.json (ICP, PSP, EVP, tone, infrastructure) and SOUL.md (voice fingerprints, banned phrases, stories you lean on) in 10 minutes. Refuses to let the operator skip — generic output is worse than no output. Loaded…
cold-email-audit
30-point audit of a B2B outbound program across four dimensions — infrastructure (8 points), targeting (8 points), messaging (8 points), and operations (6 points). Produces a 0-100 score, the top 3 levers, and a 90-day remediation order. Loaded by the main cold-email skill when the user asks to audit or grade their…
cold-email-deliverability
15-point pre-campaign domain health check across DNS (SPF, DKIM, DMARC, MX, BIMI), reputation (SNDS, Postmaster, blacklists), warm-up status (mailbox age, send volume ramp, reply ratio), and content (spam-trigger lint, link-to-text ratio, image-to-text ratio). Returns a 0-100 deliverability score and a fix-order. Uses…
cold-email-kickoff
Adaptive router for the cold-email skill pack. Detects the operator's current state (brand-config present? SOUL.md present? infrastructure ready? PSP defined? EVP locked? first campaign run?) and picks the next-best step. Loaded by the main cold-email skill on bare invocation ("/cold-email") or when the operator asks…
cold-email-list-quality
Score a cold-email prospect list 0-100 across dedup, role-fit (vs brand-config.icp), signal freshness, email-validity heuristics, exclusion-criteria match, and company-stage match. Returns the score, list of rows to remove, and a fix recommendation. Loaded by cold-email-weekly-rhythm on Monday's list refresh. Operates…