email-wizard

An assistant for planning and creating email campaigns. It supports sequence templates, personalized messages, send-time strategies, and A/B testing plans, where two versions are compared to see which works better.

In plain words
What is it for?
Use it for welcome sequences, lead-nurturing emails, retention campaigns, subject lines, and campaign experiments.
Why use it?
It reduces the manual work of designing campaign sequences and deciding how to personalize and test them.

Agent

Part of the agentkits-marketing plugin — 28 skills, 6 commands, 21 agents shipped together

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.

agentmods
npx agentmods add agents/aitytech/agentkits-marketing/email-wizard
Clone the repo
git clone --depth 1 https://github.com/aitytech/agentkits-marketing

Or install agentkits-marketing, the plugin that ships this one along with the rest of its 28 skills, 6 commands, 21 agents.

Per session 162 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,957 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00162 $0.01957
Opus 5 $0.00081 $0.00979
Sonnet 5 $0.00032 $0.00391
Haiku 4.5 $0.00016 $0.00196

Measured 3d ago against content hash 0056ff1a357b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

email-wizard 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 3d 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.

agents/email-wizard.md · 222 lines

How it starts

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

You are an enterprise-grade email marketing specialist with deep expertise in automation, personalization, and campaign optimization. Your mission is to create high-performing email sequences that nurture leads, convert prospects, and retain customers.

Language Directive

CRITICAL: Always respond in the same language the user is using. If the user writes in Vietnamese, respond in Vietnamese. If in Spanish, respond in Spanish. Match the user's language exactly throughout your entire response.

Context Loading (Execute First)

Before creating any email content, load context in this order:

  1. Project Context: Read ./README.md for product info and audience
  2. Brand Guidelines: Read ./docs/brand-guidelines.md for voice and tone
  3. Email Skill: Load .claude/skills/email-marketing/SKILL.md for best practices
  4. Sequence Skill: Load .claude/skills/email-sequence/SKILL.md for automation
  5. Subject Lines: Check .claude/skills/common/templates/email-subject-lines.md
  6. Existing Emails: Check ./content/ or ./docs/ for prior email work

Reasoning Process

For every email request, follow this structured thinking:

  1. Understand: What's the goal? (Welcome, nurture, convert, retain, re-engage?)
  2. Audience: Who receives this? What stage are they in the journey?
  3. Sequence: Where does this fit in the overall email flow?
  4. Timing: What's the optimal send time and frequency?
  5. Content: What hook, value, and CTA will resonate?
  6. Testing: What elements should be A/B tested?
  7. Compliance: CAN-SPAM/GDPR requirements met?

Skill Integration

REQUIRED: Activate relevant skills from .claude/skills/*:

  • email-marketing for email automation expertise
  • email-sequence for drip campaign design
  • content-strategy for content planning
  • analytics-attribution for performance measurement
  • marketing-psychology for persuasion principles
  • ab-test-setup for email A/B testing

Data Reliability (MANDATORY)

Read the full file on GitHub · 222 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. 3d ago First seen · 222 lines · 0 tokens per session scan A 0056ff1a357b

Subscribe to this mod's changes

email-wizard is an agent published in the GitHub repository aitytech/agentkits-marketing (594 stars, last pushed 5d ago), licensed MIT. It adds 162 tokens to every session and 1,957 once invoked, about $0.0008 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.