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/cold-emailnpx skills add jaredlangleycc/nightshift-os --skill cold-emailgit 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/cold-email)<a href="https://agentmods.dev/skills/jaredlangleycc/nightshift-os/cold-email"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/cold-email.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.00107 | $0.03760 |
| Opus 5 | $0.00053 | $0.01880 |
| Sonnet 5 | $0.00021 | $0.00752 |
| Haiku 4.5 | $0.00011 | $0.00376 |
Grade A, and why
cold-email 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 5d 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Email
Multi-touch outbound email sequences (3 to 7 touches across 10 to 21 days) to prospects who did not opt in. Different shape from the one-off cold email. The sequence wins on persistence with variety, not volume of identical sends.
This skill orchestrates the full sequence: angle development, per-touch copy, CTA ladder, send cadence, and the deliverability checks that make the difference between "in inbox" and "in spam".
When this skill triggers
- "Build a cold email sequence for [ICP]"
- "Write a 4-touch sequence"
- "Outbound sequence for [target segment]"
- "Set up cold email for [offer]"
- "How do I warm up these inboxes"
- "What should I send after the first cold email"
- "Cold email targeting [persona]"
NOT for: single first-touch (use outreach-drafter), follow-ups to existing pipeline (use follow-up-tracker), opted-in nurture (use email-sequence), broadcast newsletter (use newsletter-broadcast).
Pre-flight checks (run all before drafting)
Refuse to draft until these are answered.
Check 1: ICP locked
The sequence targets ONE ICP. Not three. Not "founders OR sales leaders OR ops people".
Need:
- Role + level (e.g., "frontline sales managers")
- Tenure or trigger ("less than 18 months in role" or "promoted in last 90 days")
- Company stage + size ("B2B SaaS, 50-500 employees")
- One specific pain you can name in their words (not yours)
If the user gives a fuzzy ICP, route them to icp-discovery first. Cold email at the wrong ICP burns the domain. Slow down.
Check 2: Offer is clear
The reply that the sequence is trying to earn must be obvious. Need:
- The CTA (research call, free coaching session, discovery call, low-friction reply)
- What the prospect gets ("30 min on your BDR ramp problem, no pitch")
- The implied next step after they say yes
If the user is still iterating on the offer, route to offer-design first.
Check 3: Volume math
Cold email is a numbers game with a ceiling on quality. Sanity-check the user's expected volume against their family floor:
What ships with it
2 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.
- 5d ago First seen · 336 lines · 107 tokens per session scan A 2a386269b695
cold-email is a skill published in the GitHub repository jaredlangleycc/nightshift-os (3 stars, last pushed 1mo ago), licensed MIT. It adds 107 tokens to every session and 3,760 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…
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.
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.
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…