email-marketing-architect

email-marketing-architect is a command for Claude Code from maigentic/stratarts. It costs 35 tokens per session (15,134 once invoked), scanned A, original, MIT.

An email marketing planning tool that covers automated email sequences, audience groups, message writing, delivery practices, and a 90-day rollout plan.

In plain words
What is it for?
Use it to plan drip campaigns, divide customers into segments, design automation workflows, write email guidelines, and map lifecycle campaigns.
Why use it?
It organizes the many decisions involved in guiding people from first contact through purchase and ongoing engagement. This reduces the need to assemble campaign ideas, audience rules, and follow-up steps separately.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the stratarts plugin — 27 commands shipped together

Good fit Use it to plan drip campaigns, divide customers into segments, design automation workflows, write email guidelines, and map lifecycle campaigns.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/maigentic/stratarts/email-marketing-architect
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/maigentic/stratarts

Made for: Claude Code.

Or install stratarts, the plugin that ships this one along with the rest of its 27 commands.

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 email-marketing-architect

README.md
[![agentmods](https://agentmods.dev/badge/commands/maigentic/stratarts/email-marketing-architect/github.svg)](https://agentmods.dev/commands/maigentic/stratarts/email-marketing-architect)
Your own site
<a href="https://agentmods.dev/commands/maigentic/stratarts/email-marketing-architect"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/email-marketing-architect/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 email-marketing-architect

Your own site · 80×15
<a href="https://agentmods.dev/commands/maigentic/stratarts/email-marketing-architect"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/email-marketing-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 15,134 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.00035 $0.15134
Opus 5 $0.00017 $0.07567
Sonnet 5 $0.00007 $0.03027
Haiku 4.5 $0.00003 $0.01513

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

Security

Grade A, and why

email-marketing-architect 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.

stratarts/commands/email-marketing-architect.md · 1,934 lines

How it starts

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

Email Marketing Architect

Step 0: Pre-Generation Verification

Before generating any output, verify these template requirements:

Template Location

  • Skeleton Template: html-templates/email-marketing-architect.html
  • Test Output Reference: skills/marketing-growth/email-marketing-architect/test-template-output.html

Required Placeholders to Replace

  • {{PRODUCT_NAME}} - Business/product name
  • {{SUBTITLE}} - Strategy summary tagline
  • {{DATE}} - Generation date
  • {{CAMPAIGN_COUNT}} - Number of automated campaigns
  • {{TOTAL_EMAILS}} - Total automated emails in system
  • {{INTERPRETATION_TITLE}} - Score interpretation headline
  • {{INTERPRETATION_TEXT}} - Detailed score explanation
  • {{VERDICT}} - Overall assessment badge
  • {{GOALS_DESCRIPTION}} - Goals section intro text
  • {{GOAL_CARDS}} - 3 goal cards HTML
  • {{JOURNEY_STAGES}} - 5 journey stage HTML blocks
  • {{CAMPAIGN_CARDS}} - Drip campaign HTML blocks
  • {{SEGMENT_CARDS}} - 3 segment cards HTML
  • {{WORKFLOW_CARDS}} - 4 workflow cards HTML
  • {{GUIDELINE_CARDS}} - 4 copywriting guideline cards HTML
  • {{METRIC_CARDS}} - 4 metric cards HTML
  • {{ROADMAP_PHASES}} - 3 phase cards HTML
  • {{CONTEXT_SIGNATURE}} - Unique session identifier

Chart Data Placeholders

  • {{JOURNEY_LABELS}} - Journey stage names for charts
  • {{JOURNEY_CONVERSION_DATA}} - Conversion rates per stage
  • {{EMAIL_VOLUME_DATA}} - Emails per journey stage
  • {{SEGMENT_LABELS}} - Segment names
  • {{SEGMENT_DATA}} - Segment percentages
  • {{SEGMENT_OPEN_DATA}} - Open rates by segment
  • {{SEGMENT_CLICK_DATA}} - Click rates by segment
  • {{PROJECTION_DATASETS}} - Performance projection data

Canonical CSS Patterns (MUST match exactly)

  • Header: header { background: #0a0a0a; padding: 0; ... } + .header-content { ... max-width: 1600px; background: linear-gradient(135deg, #10b981 0%, #14b8a6 100%); padding: 4rem 4rem 3rem 4rem; ... }
  • Score Banner: .score-banner { background: #0a0a0a; padding: 0; ... } + .score-container { display: grid; grid-template-columns: auto 1fr auto; ... max-width: 1600px; ... }
  • Footer: footer { background: #0a0a0a; ... } + .footer-content { max-width: 1600px; ... }

Read the full file on GitHub · 1,934 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. 11d ago First seen · 1,934 lines · 35 tokens per session scan A f3f613d5d5a5

Subscribe to this mod's changes

email-marketing-architect is a command published in the GitHub repository maigentic/stratarts (40 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 15,134 once invoked, about $0.0002 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.