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 Ken-Technology/cold-email-skills --skill campaign-strategygit clone --depth 1 https://github.com/Ken-Technology/cold-email-skillsWrote 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/campaign-strategy)<a href="https://agentmods.dev/skills/ken-technology/cold-email-skills/campaign-strategy"><img src="https://agentmods.dev/badge/skills/ken-technology/cold-email-skills/campaign-strategy/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/campaign-strategy"><img src="https://agentmods.dev/badge/skills/ken-technology/cold-email-skills/campaign-strategy.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.00067 | $0.03860 |
| Opus 5 | $0.00034 | $0.01930 |
| Sonnet 5 | $0.00013 | $0.00772 |
| Haiku 4.5 | $0.00007 | $0.00386 |
Grade A, and why
campaign-strategy 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 12d 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Campaign Strategy Skill
Transform client research into an actionable email strategy for a single segment. Output email sequence blueprints and AI personalization variables for the Email Copywriting skill to execute.
Output Contract
strategy.md is not machine-parsed - it's read by downstream skills (email-copywriting, prompt-writer) for context. Hard rules this skill must honor anyway, since its output flows into files that other tools read:
- AI variable names must be Title Case with spaces:
Subject Line,First Line,PS Line. They become[Title Case]brackets in emails.md and H3 headings in prompts.md - the three have to agree exactly. - AI variable names ≤30 chars (enforced in prompts.md by the prompt-writer contract).
- Never reference data sources personalization tools typically lack (news, funding, events, social media, blogs) - these propagate into prompts.md and break at runtime when the data is not available.
Required Context
Before creating a strategy, always load the client context:
- Read
{workspace}/research.md- Client research: overview, ICP, value prop, case studies, lead magnets - Read
{workspace}/notes.md(if it exists) - Client-specific preferences - Read plan.md from parent directory - Get segment definition, angle, ICP, and testing hypothesis
Directory Structure Reference ({workspace} = the client campaign workspace, default ./cold-email/{slug}/):
{workspace}/
├── research.md # Client research - ICP, value prop, case studies
├── notes.md # Optional client preferences and feedback
└── {plan_folder}/ # One per campaign, e.g. "03-15 - plan 1"
├── plan.md # Plan with ICP, segments, angles, testing hypothesis
├── 1 - {segment}/
│ └── strategy.md # THIS file - segment strategy
├── 2 - {segment}/
│ └── strategy.md
└── ...
Required Inputs
After loading context, gather:
- Segment folder path - e.g.,
{workspace}/03-15 - plan 1/1 - early-stage/ - Plan.md - Read from parent directory of segment folder to get:
- Broad ICP definition
- Segment-specific criteria
- Messaging angle for this segment
- Testing hypothesis (if any)
- Client Research Document - Check
{workspace}/research.mdor uploads - Campaign Goal - What action to drive:
- Book demos/meetings
- Drive traffic to landing page
- Get replies for qualification
- Promote lead magnet
What ships with it
4 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.
- 12d ago First seen · 401 lines · 67 tokens per session scan A 1d1b8a93b82c
campaign-strategy is a skill published in the GitHub repository Ken-Technology/cold-email-skills (3 stars, last pushed 15d ago), licensed MIT. It adds 67 tokens to every session and 3,860 once invoked, about $0.0003 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…