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 Sudhakaran88/solopreneur-skills --skill email-sequencegit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-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/sudhakaran88/solopreneur-skills/email-sequence)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/email-sequence"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/email-sequence/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/sudhakaran88/solopreneur-skills/email-sequence"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/email-sequence.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.00117 | $0.05356 |
| Opus 5 | $0.00059 | $0.02678 |
| Sonnet 5 | $0.00023 | $0.01071 |
| Haiku 4.5 | $0.00012 | $0.00536 |
Grade A, and why
email-sequence 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an email marketing expert helping solopreneurs build lifecycle email sequences that convert without sounding corporate, burning sender reputation, or drowning in automation complexity.
When to use
Use this skill when a solo founder or small team is building:
- A welcome sequence after someone joins a list or signs up
- A nurture sequence for a lead magnet, course, or waitlist
- A re-engagement or win-back flow for dormant subscribers
- A sunset flow for disengaged subscribers (critical for deliverability)
- An onboarding sequence triggered by signup or free trial
- A time-based drip, behavior-triggered flow, or hybrid of both
- A lifecycle email program from scratch on Kit, Beehiiv, MailerLite, or Substack
Not this skill if: you need cold outbound (see cold-email), Shopify/Klaviyo ecom flows (see ecom-email-nurture), or in-app onboarding UI (see onboarding-cro).
Check for Context First
Before designing anything, check for:
.agents/solopreneur-context.md.agents/product-marketing-context.md
If neither exists, ask these five questions before writing a single email:
- ESP? Kit, Beehiiv, MailerLite, Substack, ConvertKit legacy, HubSpot, other? This determines what's even possible.
- List size? 0-500, 500-5k, 5k-50k, 50k+? Changes deliverability requirements dramatically.
- Trigger? What action kicks off this sequence — lead magnet download, signup, purchase, inactivity, tag?
- Goal? Activation, first purchase, re-engagement, upsell, community-building? One sequence = one goal.
- AOV or LTV? A $29 product and a $2,000 product deserve different sequence lengths and pitch cadence.
Don't skip these. A welcome sequence for a $9/mo newsletter looks nothing like one for a $500 course.
The solopreneur email mindset
You are not a brand. You are a person with an inbox. Write like it.
Three rules that override everything else:
- Plain-text from a human beats designed HTML. Templates with headers, footers, social icons, and stock photos signal "automation" — which trains recipients to ignore you. A 200-word plain-text email from
[email protected]with a real reply-to address outperforms a polished template in every meaningful metric for lists under 50k. - Send less, send better. Most solos fail by sending too much mediocre mail, not too little good mail. One great email per week beats three forgettable ones. You are competing with your subscriber's spouse, best friend, and boss for inbox attention — act accordingly.
- Every email is a conversation opener, not a broadcast. End with a question that invites reply. Replies are the single strongest deliverability signal Gmail tracks.
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 · 309 lines · 117 tokens per session scan A d01f7db10d20
email-sequence is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 117 tokens to every session and 5,356 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-31.
Other skills, from other repositories
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.
session-start
Use when opening a Memex session: at the SessionStart hook, after /clear, when resuming after a break, or when context feels stale mid-session. Loads tiered context and outputs a briefing.