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 sanky369/vibe-building-skills --skill email-sequencesgit clone --depth 1 https://github.com/sanky369/vibe-building-skillsWrote 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/sanky369/vibe-building-skills/email-sequences)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/email-sequences"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/email-sequences/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/sanky369/vibe-building-skills/email-sequences"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/email-sequences.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.00130 | $0.02163 |
| Opus 5 | $0.00065 | $0.01081 |
| Sonnet 5 | $0.00026 | $0.00433 |
| Haiku 4.5 | $0.00013 | $0.00216 |
Grade A, and why
email-sequences 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 12d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Sequences
Write automated email sequences — fixed sets of emails sent on a schedule after a trigger (signup, purchase, launch date) — that build trust before they ask for anything. Prime directive: every email must be worth opening on its own, and every email must move the sequence's single job forward. A sequence with one job (deliver, nurture, convert, or launch) outperforms one trying to do everything; an email that only exists to "stay in touch" gets cut.
When to use / when not to
- Use for any triggered/automated email series: welcome, nurture, conversion/sales, launch, or a custom variant of these.
- If the user wants a recurring broadcast written fresh each time, that's
skills/marketing/newsletter, not an automation. - If the user has no opt-in offer generating subscribers yet, run
skills/marketing/lead-magnetfirst — a welcome sequence needs something to deliver. - If the user needs one high-stakes standalone sales page or email,
skills/marketing/direct-response-copygoes deeper on a single asset.
Intake
Ask in one batch, only what's missing:
- Trigger and goal — what event starts the sequence, and what should the subscriber do/believe by the end?
- The offer (if any) — product, price point, main objections buyers raise.
- Audience temperature — cold strangers from an ad, warm lead-magnet subscribers, or existing customers? (This sets how early you can pitch.)
- Proof assets — testimonials, case studies, results, credentials available to use. Never invent these.
- Voice — sample emails or a brand-voice guide (use
skills/marketing/brand-voiceoutput if it exists).
Infer the sequence type from the trigger (Step 1 decision rule) rather than asking. If enough is known, state assumptions and draft — don't stall.
Workflow
1. Pick the sequence architecture
Decision rule — match on trigger:
| Trigger | Sequence | Emails / span | Job |
|---|---|---|---|
| New subscriber (lead magnet, signup) | Welcome | 5 over 7 days | Deliver promise, set expectations, earn trust, introduce offer softly |
| Subscriber finished welcome, no offer live | Nurture | rotating weekly pattern | Stay valuable and top-of-mind between campaigns |
| Existing offer, warm list | Conversion | 7 over 14 days | Persuade a considered purchase |
| Something new going live on a date | Launch | 7 over ~17 days | Build anticipation, then open and close the cart |
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.
- 12d ago First seen · 134 lines · 130 tokens per session scan A bca6a8484a36
email-sequences is a skill published in the GitHub repository sanky369/vibe-building-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 130 tokens to every session and 2,163 once invoked, about $0.0006 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
dep-auditor
A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.