cold-email-sequence

cold-email-sequence is a skill for Claude Code, Codex from akiotanaka847/qaio-desktop. It costs 95 tokens per session (2,319 once invoked), scanned A, original, MIT.

A guided writing workflow for creating a three-email cold outreach sequence, one message at a time. It uses a defined format with personalized subjects, short emails, an offer, and an easy reply request.

In plain words
What is it for?
It helps write outreach to people who do not already know you, using information about the audience, your offer, and relevant proof.
Why use it?
It prevents a multi-email campaign from becoming inconsistent or relying on vague calls to action. You review and approve each message before the next one is written.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit It helps write outreach to people who do not already know you, using information about the audience, your offer, and relevant proof.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/akiotanaka847/qaio-desktop/cold-email-sequence
Install

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.

Any agent
npx skills add akiotanaka847/qaio-desktop --skill cold-email-sequence
Clone the repo
git clone --depth 1 https://github.com/akiotanaka847/qaio-desktop

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for cold-email-sequence

README.md
[![agentmods](https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/cold-email-sequence/github.svg)](https://agentmods.dev/skills/akiotanaka847/qaio-desktop/cold-email-sequence)
Your own site
<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/cold-email-sequence"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/cold-email-sequence/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.

agentmods 80×15 button for cold-email-sequence

Your own site · 80×15
<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/cold-email-sequence"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/cold-email-sequence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,319 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00095 $0.02319
Opus 5 $0.00048 $0.01159
Sonnet 5 $0.00019 $0.00464
Haiku 4.5 $0.00010 $0.00232

Measured 6d ago against content hash 497a64b00e79, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

cold-email-sequence 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 6d 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.

store/agents/outbound/.agents/skills/cold-email-sequence/SKILL.md · 237 lines

How it starts

The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cold Email Sequence

Co-write a 3-email cold outreach sequence one email at a time. The sequence follows the James Shields framework: trigger-based subject, three-sentence body, irresistible no-strings offer, one-word reply CTA. I present each draft, refine with you, and lock it before moving to the next - voice, social proof, and offer all stay tight that way.

James Shields framework - a widely-used outbound playbook that rejects the "book a demo" CTA in favor of trigger-based subjects, three-sentence bodies, free no-strings offers, and one-word reply CTAs. Optimized for reply rate, not impression count.

When to use

  • "Write me a cold email sequence for these contacts".
  • "Draft 3-email outreach for {audience}".
  • Phase 4 of either LinkedIn pipeline.
  • You have a verified contact list (from Apollo, Clay, Hunter, or anywhere else) and want fresh copy.
  • You want to refresh tired cold email copy with a proven framework.

When NOT to use

  • Warm leads who already know you - use a direct one-off email, not a 3-step cold sequence.
  • Lifecycle / onboarding / nurture for existing users - that's a different motion (and lives in the Marketing agent).
  • Transactional emails (receipts, password resets, notifications).
  • Post-call follow-ups - use the Sales agent's write-my-outreach with stage=followup.
  • Newsletters or content emails - use the Marketing agent's content skills.

Connections I need

  • None. This skill writes locally and produces a sequence file. Connections come back into play in instantly-campaign (the next phase).

Information I need

I gather the inputs in step 1 below. The minimum:

  • Trigger / source - what connects you to these leads (the LinkedIn post, the event, the news item).
  • Product - one-line description of what you sell.
  • Social proof - at least one case study with real numbers (no "10x improvement" without naming who and how). Preferably 3+ so each email gets fresh proof.
  • Offer - the free / low-friction thing you're giving away (teardown, audit, free trial, free seat).
  • Reply CTA - the one-word reply you want (defaults to "I'm in").
  • Sender - your first name only.
  • Existing draft - optional, any copy you want me to start from.

Read the full file on GitHub · 237 lines

Changes

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.

  1. 6d ago First seen · 237 lines · 95 tokens per session scan A 497a64b00e79

Subscribe to this mod's changes

cold-email-sequence is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 95 tokens to every session and 2,319 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-09-05.

Related

Other skills, from other repositories

00-gtm-router

Plan and run the full API-first GTM chain - the orchestrator (step 00) that turns an ICP description plus optional budget, volume, and urgency into the right discovery -> qualification -> extraction -> signals -> judgment -> email-resolution sequence, with per-step cost estimates and rationale, then executes it…

Zevenue/headless-gtm · 270 tokens

01-prospeo-discover

B2B company discovery and list building via the Prospeo search API. Use when the user wants to find companies from an ICP, build a prospect or TAM list, search by ICP, or size a market - e.g. "build a list of B2B SaaS in the US", "how many companies match this ICP", "TAM sizing", "company search", or any mix of…

Zevenue/headless-gtm · 139 tokens

01-prospeo-lookalike

Seed-based B2B company discovery via the Prospeo company-lookalike API. Use when the user has example companies and wants more like them - "find companies similar to X", "companies like Stripe and HubSpot", "lookalikes of these domains", "we closed these 20 logos, find more", "expand this seed list", or hands over…

Zevenue/headless-gtm · 134 tokens

05-signal-builder

Rank a prospect's outbound signals and pick the campaign approach (Pain-led / Value-led / Segment fallback) - the judgment layer (step 05) of the API-first GTM chain. Takes scraped website markdown (03-firecrawl-research), vendor signals like funding / headcount / recent hires (04-crustdata-signals), or just a URL or…

Zevenue/headless-gtm · 204 tokens

06-resolution-email-person

Turn a company domain (plus an optional person name or job title) into a verified, send-safe email address - the deliverability-first "resolution" layer of a cold-email pipeline. Use when the user wants to find or verify a work email, enrich a list or file of domains into decision-maker contacts, or resolve "who is…

Zevenue/headless-gtm · 147 tokens

01-icp-qualify

The qualification gate of the GTM chain - judges every discovered company against the client's ICP before any paid enrichment, so credits are spent only on companies that could actually buy. Works for any client and any vertical: it studies the client first, then compiles client-specific qualification criteria and…

Zevenue/headless-gtm · 176 tokens