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 classicchins/compounding-marketing --skill newsletter-growthgit clone --depth 1 https://github.com/classicchins/compounding-marketingWrote 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/classicchins/compounding-marketing/newsletter-growth)<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.
<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>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 | $0.00023 | $0.03214 |
| Sonnet 5 | $0.00009 | $0.01286 |
| Haiku 4.5 | $0.00005 | $0.00643 |
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 12d 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 — 621 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Newsletter Growth Strategy
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, runcm-contextfirst. - 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.
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.
- 12d ago First seen · 621 lines · 47 tokens per session scan A 081ea59545f8
newsletter-growth is a skill published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 6,428 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…