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 email-reviewgit 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/email-review)<a href="https://agentmods.dev/skills/ken-technology/cold-email-skills/email-review"><img src="https://agentmods.dev/badge/skills/ken-technology/cold-email-skills/email-review/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/email-review"><img src="https://agentmods.dev/badge/skills/ken-technology/cold-email-skills/email-review.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.00096 | $0.04850 |
| Opus 5 | $0.00048 | $0.02425 |
| Sonnet 5 | $0.00019 | $0.00970 |
| Haiku 4.5 | $0.00010 | $0.00485 |
Grade A, and why
email-review 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Review Skill
Review email copy against critical copy rules, QA checklists, and client preferences. Output a scored review and, if quality is sufficient, produce emails_v2.md as the final reviewed version.
Execution Tasks
Execute these tasks in order. Do NOT skip any task unless noted.
Task 1: Load Context
- Read
{segment_folder}/emails.md- The email copy to review - Read
{segment_folder}/strategy.md- Campaign strategy and goals - Read
{workspace}/research.md- ICP, value proposition, messaging themes, product info, case studies ({workspace}= the client campaign workspace folder (the orchestrator passes this path)) - Read
{workspace}/notes.md(if exists) - Client-specific preferences (HIGHEST PRIORITY)
Task 2: Load Review Reference Material
- Read
qa.mdfrom this skill folder - QA checklists and scoring criteria - Read
extra_info.mdfrom this skill folder - Exercises, tips, common mistakes - Read
../email-copywriting/references/gold-standard.md- the 9/10 bar the copy is scored against - Read
../email-copywriting/references/spam-words.md- tiered spam-word policy (NEVER/HIGH/MEDIUM + budget rule) - Read
../email-copywriting/references/sound-human.md- AI-tell lexicon/structures and the Voice Card spec - Find the ICP Voice Card in the
## Notessection ofemails.md- FLAG its absence as a violation
Task 3: Review Against Critical Copy Rules Checklist
MANDATORY: Check EVERY email against these non-negotiable rules.
Transitions & Flow (CRITICAL - top failure mode)
- No abrupt transitions from {{First Line}} to body - personalized opening flows naturally into next sentence
- FLAG any email where the static body's first sentence ignores the personalized line and jumps into a generic statement (e.g. straight into "Scaling a SaaS company..."). The body's opening must read as the next beat of the
{{First Line}}, not a topic change. - Transitional context provided or first line topic connects to body
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.
- 11d ago First seen · 263 lines · 96 tokens per session scan A e15e55b728cd
email-review is a skill published in the GitHub repository Ken-Technology/cold-email-skills (3 stars, last pushed 14d ago), licensed MIT. It adds 96 tokens to every session and 4,850 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…