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 tahirraufkeeyu/software-development-agent-stack--sdas --skill email-campaigngit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/email-campaign)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/email-campaign"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/email-campaign/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/tahirraufkeeyu/software-development-agent-stack--sdas/email-campaign"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/email-campaign.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.00068 | $0.02182 |
| Opus 5 | $0.00034 | $0.01091 |
| Sonnet 5 | $0.00014 | $0.00436 |
| Haiku 4.5 | $0.00007 | $0.00218 |
Grade A, and why
email-campaign 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Trigger this skill when the request includes any of:
- "Draft a nurture sequence for [segment]"
- "Write the onboarding emails for new signups"
- "We need a re-engagement campaign for dormant accounts"
- "Write a 3-email promotional send for the launch"
- "Turn this pillar piece into an email series"
Do not use for single transactional emails (receipts, password resets — different constraints) or one-off newsletter issues (use social-media for the newsletter snippet skill).
Inputs
Required:
- Sequence type — nurture, onboarding, re-engagement, or promotional.
- Audience segment — who is receiving it, at what stage, what they already know about us.
- Primary goal — one of: book a demo, activate a feature, drive to content, reactivate account, buy.
- Anchor content or offer — the pillar piece, feature, or promotion the sequence rides on.
Optional:
- Sender identity — person's name or company name in the "from" line.
- Brand voice source — defaults to the content-writer brand voice guide.
- Compliance region — US only (CAN-SPAM baseline), EU (GDPR + PECR), UK (UK GDPR), or global.
- Send cadence — defaults per sequence type (see below).
Outputs
A single Markdown document containing the full sequence. For each email:
- Position and purpose — e.g., "Email 2 of 5: Story."
- Send timing — e.g., "Day 3, 10am recipient local time."
- Subject line — primary + 2 A/B variants, each ≤45 characters.
- Preview text — 40-90 chars, extends the subject.
- Body copy — mobile-first (single column, short paragraphs), 80-200 words.
- Single CTA — button label + destination.
- P.S. line (optional) — short, human, reinforces the CTA or adds warmth.
- Compliance footer checklist — what must appear (physical address, unsubscribe link, etc.).
Plus a sequence summary at the top: total emails, total duration, success metric per email.
Tool dependencies
- Read access to
references/email-templates.md(required — load before drafting). - Optional: HubSpot MCP for list segment counts and historical open/click benchmarks.
- Optional: content-writer brand voice guide for tone consistency.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 214 lines · 68 tokens per session scan A 277223daeda5
email-campaign is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 2,182 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…