newsletter-monetization-planner

newsletter-monetization-planner is a skill for Claude Code from aaron-he-zhu/aaron-marketing-skills. It costs 139 tokens per session (3,577 once invoked), scanned A, original, Apache-2.0.

A revenue-planning tool for earning money from a newsletter or other owned audience, such as a creator email list.

In plain words
What is it for?
Use it to plan paid subscription tiers, sponsorship inventory and pricing, referral loops, and projections linking subscriber growth to revenue.
Why use it?
It shows how subscriptions, sponsorships, advertising rates, and referrals could relate to list growth and revenue while including offer and disclosure checks.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Claude Code; built for openclaw.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is Emit the standard shape from [skill-contract.md §Handoff Summary Format](../../../references/skill-contract.md): Status, Objective, Key Findings / Output, Evide.

Part of the aaron-marketing plugin — 120 skills shipped together , and of aaron-marketing

Good fit Use it to plan paid subscription tiers, sponsorship inventory and pricing, referral loops, and projections linking subscriber growth to revenue.

Compare 6 skills from other repositories ↓
About the project

aaron-marketing-skills is a collection of 120 AI-agent skills covering marketing work such as brand narrative, search optimization, social media, email, advertising, influencer campaigns, and launches. Marketers and agent users can install it as a plugin, use its portable skills, or run its described bot team. The catalogue entries are components of this marketing workflow.

aaron-he-zhu/aaron-marketing-skills · 2,767 stars · on GitHub · aaronmarketing.ai

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills
agentmods
npx agentmods add skills/aaron-he-zhu/aaron-marketing-skills/newsletter-monetization-planner

Made for: Claude Code.

Or install aaron-marketing, the plugin that ships this one along with the rest of its 120 skills.

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.

agentmods badge for newsletter-monetization-planner

README.md
[![agentmods](https://agentmods.dev/badge/skills/aaron-he-zhu/aaron-marketing-skills/newsletter-monetization-planner/github.svg)](https://agentmods.dev/skills/aaron-he-zhu/aaron-marketing-skills/newsletter-monetization-planner)
Your own site
<a href="https://agentmods.dev/skills/aaron-he-zhu/aaron-marketing-skills/newsletter-monetization-planner"><img src="https://agentmods.dev/badge/skills/aaron-he-zhu/aaron-marketing-skills/newsletter-monetization-planner/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.

agentmods 80×15 button for newsletter-monetization-planner

Your own site · 80×15
<a href="https://agentmods.dev/skills/aaron-he-zhu/aaron-marketing-skills/newsletter-monetization-planner"><img src="https://agentmods.dev/badge/skills/aaron-he-zhu/aaron-marketing-skills/newsletter-monetization-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,577 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. Third-party audits
  • Socket pass 2 Sept 2026
  • Snyk warn 2 Sept 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 83
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00139 $0.03577
Opus 5 $0.00069 $0.01788
Sonnet 5 $0.00028 $0.00715
Haiku 4.5 $0.00014 $0.00358

Measured 10d ago against content hash e38e5914781b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

newsletter-monetization-planner 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 10d 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.

email/nurture/newsletter-monetization-planner/SKILL.md · 115 lines

How it starts

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

Newsletter Monetization Planner

Plans the money and growth-loop economics for an owned-audience program — a newsletter or creator list — across three revenue lines: paid-subscription tiers, ad/sponsorship inventory with a rate card, and referral/recommendation loops. This is the build skill for the SEND D (Direct-response / Conversion) lever on owned audiences: it produces the revenue model, the list-growth ↔ revenue projection, and the honest-offer / disclosure checks. It does not compute the profile-weighted EQS or run the D1 veto (that is email-quality-auditor), and it delegates the return math to roi-calculator and the post-click page to landing-optimizer.

Scope guard: this skill plans monetization and growth economics only — it scores/handles the SEND-D owned-audience lever and hands off. It does not compute the final EQS, run any of S1/S2/N1/D1, or do the return math itself. Only email-quality-auditor computes EQS and enforces the vetoes; roi-calculator owns revenue-per-send / list-value math as the SSOT.

Quick Start

Shortest invocation:

Model monetization for my 20,000-subscriber newsletter — paid tiers and sponsorships

Common scenario:

Build a sponsorship rate card and a paid-sub revenue model for a 45K list at 42% open / 3.1% click — compare a paid-sub-only vs a hybrid (subs + sponsorship) plan

Output: a labeled revenue model (paid-tier table + ad/sponsorship CPM-or-flat rate card + referral-loop line), a list-growth ↔ revenue projection, and a disclosure / honest-offer checklist — with every projected number tagged Measured / User-provided / Estimated.

Skill Contract

  • Reads: list size and active-subscriber count, open / click / CTOR (from a ~~email platform own-data export), current send cadence, existing revenue lines, the monetization goal (paid-subs / sponsorship / both), any target revenue or price points, and a growth rate or acquisition source. Offer terms and approved wording from memory/claims/claims-ledger.md and memory/claims/offers.md — the offer-claims-registry ledger — when present. Consent/suppression state (who may be mailed a commercial offer) from consent-registry (memory/consent/) when present.
  • Writes: a user-facing revenue model and growth ↔ revenue projection plus the disclosure/honest-offer checklist, and a reusable handoff summary. Save path: memory/email/newsletter-monetization-planner/YYYY-MM-DD-<topic>.md.
  • Promotes: the chosen monetization mix, locked price points, the sponsorship rate basis (CPM vs flat), and any unsubstantiated-claim or missing-disclosure risk — ask before writing, then promote durable facts to memory/hot-cache.md and propose price/mix decisions as pending-decision items in memory/open-loops.md.
  • Done when:
    1. The revenue model covers each active line (paid tiers and/or sponsorship inventory and/or referral loop) with a stated conversion or fill-rate assumption per line.
    2. Every projected number is labeled Measured / User-provided / Estimated, and no revenue figure is presented as measured when it rests on an assumed conversion rate.
    3. The growth ↔ revenue projection names at least one loop (referral / recommendation / boost) and its assumed input.
    4. The disclosure/honest-offer checklist is completed: every sponsorship is labeled as an ad, and any claim needing substantiation is flagged for D1, not asserted.
  • Primary next skill: roi-calculator — turn the revenue model into revenue-per-send / list-value / payback math, or email-quality-auditor to score the program and run D1.

Read the full file on GitHub · 115 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.

  1. 10d ago Changed e38e5914781b
  2. 13d ago First seen · 115 lines · 139 tokens per session scan A 93eaf217b05a

Subscribe to this mod's changes

newsletter-monetization-planner is a skill published in the GitHub repository aaron-he-zhu/aaron-marketing-skills (2,767 stars, last pushed today), licensed Apache-2.0. It adds 139 tokens to every session and 3,577 once invoked, about $0.0007 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-30.