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 agentmods add skills/jaredlangleycc/nightshift-os/email-sequencenpx skills add jaredlangleycc/nightshift-os --skill email-sequencegit clone --depth 1 https://github.com/jaredlangleycc/nightshift-osWrote 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/jaredlangleycc/nightshift-os/email-sequence)<a href="https://agentmods.dev/skills/jaredlangleycc/nightshift-os/email-sequence"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/email-sequence.svg" alt="Measured on agentmods" 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 | $0.00103 | $0.03315 |
| Opus 5 | $0.00051 | $0.01657 |
| Sonnet 5 | $0.00021 | $0.00663 |
| Haiku 4.5 | $0.00010 | $0.00331 |
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 3d 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Sequence
Lifecycle email design for solopreneurs. Welcome series, nurture flows, re-engagement, win-back. The goal is to move a subscriber from cold opt-in to warm conversation in the smallest number of emails that respect their attention.
Most solopreneur email sequences fail in one of two ways: too long (15 emails when 5 would have converted), or too generic (every brand sounds the same). This skill cuts both.
When this skill triggers
- "Write a welcome series for [lead magnet]"
- "Build a nurture sequence"
- "Drip campaign for new subscribers"
- "Onboarding emails for [product]"
- "Re-engagement sequence for cold subscribers"
- "Win-back emails"
- "5-email series after the lead-gen assessment"
- "Lifecycle flow for [audience]"
NOT for: cold outreach to people who didn't opt in (use cold-email), one-off sends to the full list (use newsletter-broadcast), single-purpose transactional emails like receipts (the user's tool handles those).
The diagnostic before drafting
Coach-mode first. Don't open a doc. Ask one at a time.
Sequence-purpose questions
- "What did the subscriber just do that triggered this sequence?" (Took the lead-gen assessment, signed up for a lead magnet, joined the newsletter, became a customer, went cold for 60 days.)
- "What's the one action you want them to take by the end of the sequence?" (Book a call, buy the offer, reply to one email, click through to a specific page.)
- "What do they believe right now, and what do they need to believe to take that action?"
- "How warm is this list? Did they double opt-in, single opt-in, or import from a CSV?"
If the user can't name the one action they want by the end, stop. Hand back to offer-design or business-coach. A nurture without a destination is a treadmill.
The 4 lifecycle sequences
A solopreneur typically runs 4 sequences. Pick the one the user is building. Each has a distinct shape.
1. Welcome series (post lead magnet opt-in)
Trigger: subscriber takes a lead magnet (lead-gen assessment, free guide, scorecard).
What ships with it
5 files 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.
- 3d ago First seen · 334 lines · 103 tokens per session scan A f6f341ee1a92
email-sequence is a skill published in the GitHub repository jaredlangleycc/nightshift-os (3 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 3,315 once invoked, about $0.0005 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
Brand Guidelines Generator
Create and maintain brand style guides for consistent visual identity.
web-vid
Turn a web app or marketing site into a recreated (not screen-recorded) Remotion promo video — pixel-faithful to the site's own design system, choreographed clicks/scrolls/zooms, rendered to MP4. Use when the user asks for a product demo video, a promo/teaser for LinkedIn or social, an "walkthrough video" of their…
demo-video-factory
Generate a custom 26s product-demo video from any SaaS URL — brand-matched scenes, a recreated product-UI "wow" scene, real screenshots, and a soundtrack. Use whenever the user wants a demo, promo, launch, or marketing video for a website or product.
pitchdocs
Generate marketing-quality repository documentation from codebase analysis. Scans 10 signal categories, extracts features with file-level evidence, and produces README, CHANGELOG, ROADMAP, and 15+ more docs. Zero runtime dependencies. For AI context file management, see ContextDocs.
brand
Brand context management for marketing sessions with continuity across conversations.
liking-factor-engineer
Analyze and engineer liking to increase rapport, persuasion, and compliance in marketing, sales, and communication contexts. Use this skill when the user wants to improve how much an audience likes them, their brand, or their message — including writing sales copy, designing onboarding flows, crafting brand voice…