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.
npx skills add brainbytes-dev/everything-claude-marketing --skill email-automationgit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketingWrote 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.
[](https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/email-automation)<a href="https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/email-automation"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/email-automation/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.
<a href="https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/email-automation"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/email-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00025 | $0.03134 |
| Opus 5.5 | $0.00010 | $0.01254 |
| Sonnet 5.5 | $0.00005 | $0.00627 |
| Haiku 4.5 | $0.00003 | $0.00313 |
Grade A, and why
email-automation 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Automation
When to Activate
Use this skill when:
- Building marketing automation workflows
- Designing trigger-based email flows
- Integrating email with SMS, push, or other channels
- Setting up lead scoring systems
- Evaluating automation platforms
- Documenting and testing complex workflows
- Optimizing existing automation for performance
First Questions
Before building automation, clarify:
- What is the business goal of this automation? (Convert leads, onboard users, retain customers, recover revenue)
- What triggers should start the workflow? (Form submit, purchase, behavior, date)
- What channels are available? (Email, SMS, push notifications, in-app messages, direct mail)
- What data is available to personalize and branch logic?
- What platform is being used? (HubSpot, Klaviyo, ActiveCampaign, Mailchimp, Customer.io, etc.)
- Who owns and maintains the workflow after launch?
- Are there existing workflows that could conflict?
Core Rules
- Start with the outcome, work backwards. Define the desired end action first, then map the path to get there.
- Simple workflows that run > complex workflows that break. Start with linear flows. Add branching only when data proves it's needed.
- Every workflow needs an owner. Someone must be responsible for monitoring, optimizing, and updating.
- Test in isolation before connecting. Test each workflow independently before linking it to other workflows.
- Document everything. Workflow logic that lives only in the platform interface is unmaintainable. Create external documentation.
- Set review dates. Every workflow should be reviewed quarterly. Stale automations send irrelevant emails.
- Respect channel preferences. Just because you CAN send SMS doesn't mean the subscriber wants SMS. Always honor opt-in by channel.
Automation Triggers
Event-Based Triggers
| Trigger | Use Case | Example Workflow |
|---|---|---|
| Form submission | Lead magnet delivery, contact form follow-up | Welcome sequence + lead magnet delivery |
| Product purchase | Post-purchase experience | Thank you, onboarding, cross-sell |
| Cart abandonment | Revenue recovery | 3-email abandoned cart sequence |
| Trial signup | User activation | Onboarding sequence with feature education |
| Webinar registration | Event nurture | Pre-event reminders, post-event follow-up |
| Support ticket closed | Customer satisfaction | Feedback survey, knowledge base recommendation |
| Subscription cancellation | Churn recovery | Exit survey + winback offer |
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.
- 2mo ago First seen · 348 lines · 25 tokens per session scan A 34865d0f68ef
email-automation is a skill published in the GitHub repository brainbytes-dev/everything-claude-marketing (10 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 3,134 once invoked, about $0.0001 per session on Opus 5.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-03.
email-automation compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| email-automationbrainbytes-dev/everything-claude-marketing | Skill | 10 | 7mo ago | MIT | A | 25 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |