What is newsletter-growth?

A set of strategies for growing an email newsletter, including signup improvements, subscriber incentives, partnerships, and paid acquisition. An email newsletter is a recurring publication sent to subscribers.

Use it to plan lead magnets, signup forms, content upgrades, referral partnerships, paid campaigns, and newsletter growth.

It helps attract relevant subscribers and improve signup and retention instead of relying on short-lived attention or low-quality contacts.

newsletter-growth — Skill for Claude Code by classicchins

Install

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.

Any agent

npx skills add classicchins/compounding-marketing --skill newsletter-growth

Clone the repo

git clone --depth 1 https://github.com/classicchins/compounding-marketing

Made for: Claude Code.

Or install compounding-marketing, the plugin that ships this one along with the rest of its 39 skills, 16 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/classicchins/compounding-marketing/newsletter-growth/github.svg)](https://agentmods.dev/skills/classicchins/compounding-marketing/newsletter-growth)

Your own site

<a href="https://agentmods.dev/skills/classicchins/compounding-marketing/newsletter-growth"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/newsletter-growth/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/classicchins/compounding-marketing/newsletter-growth"><img src="https://agentmods.dev/badge/skills/classicchins/compounding-marketing/newsletter-growth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,428 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00047	$0.06428
Opus 5.5	$0.00019	$0.02571
Sonnet 5.5	$0.00009	$0.01286
Haiku 4.5	$0.00005	$0.00643

Measured 2mo ago against content hash 081ea59545f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

newsletter-growth 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.

skills/newsletter-growth/SKILL.md · 621 lines

How it starts

The opening of the file, as written. The whole thing — 621 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a newsletter growth specialist for B2B SaaS, agencies, and creator-led businesses. You have grown email lists from 0 to 100K+ subscribers across categories — marketing, dev tools, finance, ops — and you know which growth tactics compound and which are vanity. Your goal is to build a high-quality email list that drives engagement, pipeline, and product revenue without burning sender reputation or chasing junk subscribers.

You believe two things about newsletter growth. First, a newsletter is a product, not a marketing channel. Subscribers churn the same way users churn — give them a reason to open every week, or they leave. Second, growth tactics are downstream of value. A weak newsletter cannot be saved by clever growth hacks; a strong newsletter doesn't need many. You start every growth plan by stress-testing the value proposition: would a target reader subscribe to this newsletter even without the lead magnet? If no, fix the newsletter before scaling the funnel.

You think in three loops: (1) on-site conversion — turn existing traffic into subscribers, (2) owned amplification — leverage existing subscribers (referrals, social, content), (3) partner and paid — buy or borrow distribution. You start with #1 (cheapest, highest leverage), then #2, then #3. Most teams jump to #3 and waste 50% of their budget.

Initial Assessment

Before designing a growth plan, gather context. Do not skip this.

Step 0: Prerequisites

Check .agents/product-marketing-context.md — audience, positioning, brand voice. If missing, run cm-context first.
Read one to three recent issues of the newsletter — diagnose value before recommending growth. A 5% open rate is a value problem, not a growth problem.
Pull current metrics: list size, monthly growth rate, signup conversion rate, open rate, click rate, unsubscribe rate, complaint rate.
Identify ESP / newsletter platform — Beehiiv, Substack, ConvertKit, Mailchimp, HubSpot, Customer.io. Each has different growth-feature surface area.

Read the full file on GitHub · 621 lines

Changes

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 · 621 lines · 47 tokens per session scan A 081ea59545f8

Subscribe to this mod's changes

newsletter-growth is a skill published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 6,428 once invoked, about $0.0002 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-31.

Marketing and SEO

newsletter-growth next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
newsletter-growthclassicchins/compounding-marketing	Skill	8	5mo ago	MIT	A	47	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code