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 jamditis/claude-skills-journalism --skill newsletter-publishinggit clone --depth 1 https://github.com/jamditis/claude-skills-journalismWrote 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/jamditis/claude-skills-journalism/newsletter-publishing)<a href="https://agentmods.dev/skills/jamditis/claude-skills-journalism/newsletter-publishing"><img src="https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/newsletter-publishing/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/jamditis/claude-skills-journalism/newsletter-publishing"><img src="https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/newsletter-publishing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.04204 |
| Opus 5.5 | $0.00010 | $0.01682 |
| Sonnet 5.5 | $0.00005 | $0.00841 |
| Haiku 4.5 | $0.00002 | $0.00420 |
Grade A, and why
newsletter-publishing 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 2mo 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 — 577 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Newsletter publishing
Practical workflows for building and managing email newsletters for journalism and academia.
When to activate
- Creating a new newsletter from scratch
- Designing email templates for journalism content
- Building and segmenting subscriber lists
- Analyzing newsletter performance metrics
- Planning editorial calendars for newsletters
- Migrating between newsletter platforms
- Improving deliverability and open rates
Newsletter architecture
Content strategy framework
## Newsletter strategy document
### Core identity
- **Name**:
- **Tagline** (one line):
- **What readers get**: [specific value proposition]
- **Frequency**: [ ] Daily [ ] Weekly [ ] Bi-weekly [ ] Monthly
### Target audience
- Primary reader:
- What they care about:
- Why they'll subscribe:
- What they'll do with this info:
### Content pillars
1. [Core topic 1] - [how often]
2. [Core topic 2] - [how often]
3. [Recurring feature] - [how often]
### Voice and tone
- Formal ↔ Conversational: [1-5]
- Serious ↔ Light: [1-5]
- Reported ↔ Personal: [1-5]
### Success metrics (first 6 months)
- Subscriber goal:
- Target open rate:
- Target click rate:
Issue structure template
## [Newsletter Name] - Issue #[XX]
**Date**: [Date]
**Subject line**: [Subject]
**Preview text**: [First 50-90 characters readers see]
---
### Opening hook
[2-3 sentences that make readers want to keep reading]
### Main story
[Your primary content - 300-600 words for most newsletters]
### Secondary items (if applicable)
- **Quick hit 1**: [Brief item with link]
- **Quick hit 2**: [Brief item with link]
### Recurring section
[Weekly column, data point, recommendation, etc.]
### Sign-off
[Personal note, call to action, or preview of next issue]
---
**Unsubscribe** | **Preferences** | **Forward to a friend**
Technical implementation
HTML email template (responsive)
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>{{newsletter_name}}</title>
<style>
/* Reset styles for email clients */
body { margin: 0; padding: 0; width: 100%; }
table { border-collapse: collapse; }
img { border: 0; display: block; }
/* Responsive container */
.container {
max-width: 600px;
margin: 0 auto;
font-family: Georgia, serif;
font-size: 18px;
line-height: 1.6;
color: #333;
}
/* Dark mode support */
@media (prefers-color-scheme: dark) {
.container { background-color: #1a1a1a; color: #e0e0e0; }
a { color: #6db3f2; }
}
/* Mobile styles */
@media only screen and (max-width: 480px) {
.container { padding: 15px !important; }
h1 { font-size: 24px !important; }
}
</style>
</head>
<body>
<table role="presentation" width="100%">
<tr>
<td align="center" style="padding: 20px;">
<div class="container">
<!-- Header -->
<table width="100%">
<tr>
<td style="padding-bottom: 20px; border-bottom: 2px solid #333;">
<h1 style="margin: 0;">{{newsletter_name}}</h1>
<p style="margin: 5px 0 0; color: #666;">{{issue_date}}</p>
</td>
</tr>
</table>
<!-- Content -->
<table width="100%">
<tr>
<td style="padding: 30px 0;">
{{content}}
</td>
</tr>
</table>
<!-- Footer -->
<table width="100%">
<tr>
<td style="padding-top: 20px; border-top: 1px solid #ddd; font-size: 14px; color: #666;">
<p>You're receiving this because you subscribed to {{newsletter_name}}.</p>
<p>
<a href="{{unsubscribe_url}}">Unsubscribe</a> |
<a href="{{preferences_url}}">Update preferences</a>
</p>
</td>
</tr>
</table>
</div>
</td>
</tr>
</table>
</body>
</html>
What ships with it
1 file 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.
- 2mo ago First seen · 577 lines · 24 tokens per session scan A 5db74f2d492d
newsletter-publishing is a skill published in the GitHub repository jamditis/claude-skills-journalism (448 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 4,204 once invoked, about $0.0001 per session on Opus 5.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.
newsletter-publishing compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| newsletter-publishingjamditis/claude-skills-journalism | Skill | 448 | 2d ago | MIT | A | 24 | Claude Code, Codex |
| running-cluster-experimentschgagne/claude-skills-research | Skill | 5 | yesterday | MIT | A | 72 | Claude Code, Codex |
| explaining-derivationschgagne/claude-skills-research | Skill | 5 | yesterday | MIT | A | 109 | Claude Code, Codex |
| self-surveying-literaturechgagne/claude-skills-research | Skill | 5 | yesterday | MIT | A | 136 | Claude Code, Codex |
| food-researchPangenomeAI/academic-skills-food-nutrition | Skill | 41 | 2mo ago | MIT | A | 154 | Claude Code |
| data-table-formatterur-grue/autopunk-media-skills | Skill | 43 | 2mo ago | MIT | A | 46 | Claude Code |
| food-chemistryPangenomeAI/academic-skills-food-nutrition | Skill | 41 | 2mo ago | MIT | A | 110 | Claude Code |