A command for designing an email automation workflow from an initial brief. It maps the audience, trigger, timing, conditions, and message sequence around a goal and measurement.

Use it to plan lead-generation or online-store email flows, including audience segments, exclusions, delays, branching rules, and campaign goals.

It turns a broad email-marketing idea into a structured workflow and highlights missing information before the workflow is designed.

gtm-email — Command for Claude Code by uppifyagency

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/uppifyagency/bettercallclaudegrowth

Made for: Claude Code.

Or install bettercallclaudegrowth, the plugin that ships this one along with the rest of its 9 skills, 11 commands, 3 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm-email/github.svg)](https://agentmods.dev/commands/uppifyagency/bettercallclaudegrowth/gtm-email)

Your own site

<a href="https://agentmods.dev/commands/uppifyagency/bettercallclaudegrowth/gtm-email"><img src="https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm-email/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/uppifyagency/bettercallclaudegrowth/gtm-email"><img src="https://agentmods.dev/badge/commands/uppifyagency/bettercallclaudegrowth/gtm-email.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 562 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.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.00562
Opus 5	$0.00014	$0.00281
Sonnet 5	$0.00006	$0.00112
Haiku 4.5	$0.00003	$0.00056

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

Security

Grade A, and why

gtm-email 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.

bettercallclaudegrowth/commands/gtm-email.md · 30 lines

How it starts

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

/gtm-email - Email automation workflow

This command applies the advanced-email-marketing skill.

Always respect userConfig.output_language (IT default), userConfig.industry, userConfig.brand_voice and userConfig.default_channel.

Steps

Load the skill. Invoke the advanced-email-marketing skill by name (it activates from its description; do not use file paths) and apply its frameworks, going deeper with cheatsheets, patterns and the relevant chapter (RFM, advanced segments, specific flow) when needed. Do NOT copy the books' content: use it only to reason.
Frame the input. Analyze $ARGUMENTS and the industry to understand the scenario (lead-gen vs e-commerce), the goal of the flow and the audience. If essential data is missing (product cycle, desired length, exclusions), ask 1-2 targeted questions before proceeding.
Apply the frameworks. Work in the order of the workflow grammar: start from the customer journey and choose the correct activation trigger among the 8 triggers. Define the segment (via RFM segmentation for e-commerce or scoring for lead-gen) and the excluded ones. Set delays, if/then and branching. Model the right flow among welcome / drip / abandoned cart / winback (and its related Sunset). Verify deliverability, GDPR compliance and plan at least one A/B test on subject or timing.
Produce the structured output in the brand_voice:
- Goal + KPI (and who to EXCLUDE)
- Segment (definition + size check)
- Trigger / Enrollment (exact condition with AND/OR/NOT, one-time entry or always-on)
- Email sequence: for each -> delay, if/then branch, subject + preview text, content angle, CTA
- Operational notes: deliverability, GDPR/consent, dynamic vs static coupon, planned A/B test

Close with the skill's pre-launch checklist as a final check before activation.

Red-team (optional). Invoke the gtm-critic agent to stress-test the flow (offer↔email message consistency, frictions and exit points, deliverability/GDPR, correct trigger), then integrate the fixes.

Read the full file on GitHub · 30 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.

10d ago First seen · 30 lines · 28 tokens per session scan A bc851d6b94ce

Subscribe to this mod's changes

gtm-email is a command published in the GitHub repository uppifyagency/bettercallclaudegrowth (5 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 562 once invoked, about $0.0001 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.

Claude Code Marketing and SEO ai-marketing anthropic b2b-saas claude-code-plugin coaching

recall-save

Generate / overwrite .recall/context.md with Recall's local offline summarizer.

raiyanyahya/recall · 15 tokens

notebook-query

Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…

MarcosNahuel/antigravity-plugin-cc · 74 tokens

gtm-email

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/gtm-email - Email automation workflow

Steps

What this file has done since we first saw it

Other commands, from other repositories

recall-save

notebook-query

ccc-orchestrate

standup

audit-project-github

design