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 jaredlangleycc/nightshift-os --skill newsletter-broadcastgit 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/newsletter-broadcast)<a href="https://agentmods.dev/skills/jaredlangleycc/nightshift-os/newsletter-broadcast"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/newsletter-broadcast/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/jaredlangleycc/nightshift-os/newsletter-broadcast"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/newsletter-broadcast.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.00102 | $0.03298 |
| Opus 5 | $0.00051 | $0.01649 |
| Sonnet 5 | $0.00020 | $0.00660 |
| Haiku 4.5 | $0.00010 | $0.00330 |
Grade A, and why
newsletter-broadcast 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 11d 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Newsletter Broadcast
The single weekly broadcast send. Different from a sequence (no automation, no drip) and different from a transactional email. It's a content piece, delivered to the inbox, where the user shows up with one idea per week.
For solopreneurs, the newsletter is the owned channel. Social can disappear overnight. The list goes with the user.
When this skill triggers
- "Draft this week's newsletter"
- "Sunday newsletter"
- "Send to the lead-gen assessment Leads"
- "Broadcast to my list"
- "Send the weekly"
- "Newsletter from this week's essay"
- "Weekly email"
NOT for: drip / automation sequences (use email-sequence), cold outreach (use cold-email), one-to-one client emails (use outreach-drafter or just write it).
The format spec
Each issue. Same shape. Different content. Repetition of structure is what trains the reader.
SUBJECT
5 to 9 words. State, don't sell. Sounds like a friend wrote it.
PREHEADER
5 to 12 words. Continues the subject.
GREETING
First name. No "Dear" or "Hi there".
PERSONAL FRAME
1 to 2 paragraphs. What the user is sitting with this week. Tied to a moment
from the last 7 days (a client call, a Saturday morning, a moment in the car
with a kid, a piece of news).
THE ESSAY (or main body)
500 to 600 words. The core idea this week. If this is the spine pattern,
the body is the blog essay pulled in.
ONE LINE BRIDGE
1 sentence. Lands the essay's takeaway.
SOFT CTA
One link. Specific. ("Take the lead-gen assessment" not "Learn more.")
SIGN-OFF
First name. No title.
P.S. (optional)
One specific line. Use sparingly.
Hard cap: 700 words total. Inbox is a glance, not a sit-down read.
Target: 500 words. Most weeks the user will write longer than they need to. Cut.
The Sunday spine pattern
The newsletter is the cap of the Sunday Spine Workflow (see content-strategy/references/repurposing-spine.md).
Sunday morning:
- Finalize the blog essay (written earlier in the week).
- Write the personal frame on top (10 to 20 minutes).
- Strip the essay to fit the 500 to 600 word newsletter window.
- Add the soft CTA.
- Send.
What ships with it
4 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.
- 11d ago First seen · 367 lines · 102 tokens per session scan A 01fd447c4358
newsletter-broadcast is a skill published in the GitHub repository jaredlangleycc/nightshift-os (3 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 3,298 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…