cold-email-outreach

cold-email-outreach is a cursor rule for Cursor from thatrebeccarae/claude-marketing. It costs 53 tokens per session (1,273 once invoked), scanned A, original, MIT.

A guide for planning unsolicited business email campaigns and follow-up sequences. It covers message structure, sending reputation, email authentication, delivery checks, and CAN-SPAM and GDPR compliance.

In plain words
What is it for?
Use it to write cold-email sequences, plan follow-up timing, check SPF, DKIM, and DMARC settings, and review bounce, complaint, open, and reply rates.
Why use it?
It helps reduce the chance that outreach emails are rejected, marked as spam, or sent in ways that break privacy and marketing rules. It also provides a way to plan follow-ups instead of sending them randomly.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it to write cold-email sequences, plan follow-up timing, check SPF, DKIM, and DMARC settings, and review bounce, complaint, open, and reply rates.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/thatrebeccarae/claude-marketing/cold-email-outreach
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.

Clone the repo
git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing

Made for: Cursor.

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-outreach

README.md
[![agentmods](https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/cold-email-outreach/github.svg)](https://agentmods.dev/rules/thatrebeccarae/claude-marketing/cold-email-outreach)
Your own site
<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/cold-email-outreach"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/cold-email-outreach/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-outreach

Your own site · 80×15
<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/cold-email-outreach"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/cold-email-outreach.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,273 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.00053 $0.01273
Opus 5 $0.00026 $0.00636
Sonnet 5 $0.00011 $0.00255
Haiku 4.5 $0.00005 $0.00127

Measured 10d ago against content hash 57ae659912fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

cold-email-outreach 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 10d 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.

integrations/cursor/cold-email-outreach.mdc · 144 lines

How it starts

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

Cold Email & Outreach

Design, optimize, and scale cold email outreach with high deliverability and compliance.

Deliverability Fundamentals

Authentication (Required)

Record Purpose Check
SPF Authorizes sending servers dig TXT domain.com
DKIM Cryptographic message signing DKIM selector lookup
DMARC Policy for failed auth dig TXT _dmarc.domain.com

Domain Warming

New domains or IPs need gradual volume ramp:

Week Daily Volume Notes
1 5-10 Known contacts only
2 15-25 Mix of known and new
3 30-50 Monitor bounce/spam rates
4 50-100 Scale if rates healthy
5+ 100-200 Max per domain/day

Dedicated sending domain: Use a subdomain (outreach.company.com) to protect your primary domain reputation.

Health Benchmarks

Metric Healthy Warning Critical
Bounce rate <2% 2-5% >5%
Spam complaint <0.1% 0.1-0.3% >0.3%
Open rate >40% 20-40% <20%
Reply rate >5% 2-5% <2%

Sequence Design

Optimal Sequence Structure

Email 1 (Day 0)  — Value-first introduction
Email 2 (Day 3)  — Follow-up with new angle
Email 3 (Day 7)  — Social proof / case study
Email 4 (Day 14) — Breakup email (last attempt)

Timing

  • Best send days: Tuesday, Wednesday, Thursday
  • Best send times: 8-10am recipient timezone
  • Avoid: Monday morning, Friday afternoon, weekends
  • Follow-up spacing: 3-5 days between emails (never daily)

Subject Line Formulas

Formula Example Open Rate
Question "Quick question about [company] growth?" High
Mutual connection "Saw your talk at [event]" Very high
Specific result "[Company] could save $40K/year on [X]" High
Curiosity "Idea for [specific initiative]" Medium-high
Direct "15-min call about [pain point]?" Medium

Read the full file on GitHub · 144 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. 10d ago First seen · 144 lines · 53 tokens per session scan A 57ae659912fa

Subscribe to this mod's changes

cold-email-outreach is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (134 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,273 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-30.