newsletter-audience-segmenter

newsletter-audience-segmenter is a skill for Claude Code from ur-grue/autopunk-media-skills. It costs 36 tokens per session (2,569 once invoked), scanned A, original, MIT.

A brief that divides a newsletter's subscribers into three to five groups and suggests content and messages for each group. Audience segmentation means treating groups of readers differently based on their interests or behaviour.

In plain words
What is it for?
Use it to plan targeted editions, paid tiers, sponsored content, or an explanation of the audience for advertisers.
Why use it?
It helps replace one message for everyone with clearer content choices for different kinds of subscribers.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the autopunk-media-skills plugin — 187 skills shipped together

Good fit Use it to plan targeted editions, paid tiers, sponsored content, or an explanation of the audience for advertisers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ur-grue/autopunk-media-skills/newsletter-audience-segmenter
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 ur-grue/autopunk-media-skills --skill newsletter-audience-segmenter
Clone the repo
git clone --depth 1 https://github.com/ur-grue/autopunk-media-skills

Made for: Claude Code.

Or install autopunk-media-skills, the plugin that ships this one along with the rest of its 187 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-audience-segmenter

README.md
[![agentmods](https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/newsletter-audience-segmenter/github.svg)](https://agentmods.dev/skills/ur-grue/autopunk-media-skills/newsletter-audience-segmenter)
Your own site
<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/newsletter-audience-segmenter"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/newsletter-audience-segmenter/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-audience-segmenter

Your own site · 80×15
<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/newsletter-audience-segmenter"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/newsletter-audience-segmenter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,569 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
  • NVIDIA SkillSpector pass 7 Sept 2026
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.00036 $0.02569
Opus 5 $0.00018 $0.01285
Sonnet 5 $0.00007 $0.00514
Haiku 4.5 $0.00004 $0.00257

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

Security

Grade A, and why

newsletter-audience-segmenter 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 8d 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/strategy/newsletter-audience-segmenter/SKILL.md · 142 lines

How it starts

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

Newsletter Audience Segmenter

What This Skill Does

Produces a practical audience segmentation brief for a newsletter, identifying 3-5 distinct subscriber groups with tailored content recommendations and messaging strategies for each segment.

When To Use This Skill

  • You are launching a new newsletter and need to define your audience segments before writing your first edition
  • Your subscriber list has grown and a one-size-fits-all approach is no longer working — open rates or engagement are declining
  • You are introducing paid tiers, sponsored content, or targeted editions and need to understand which subscribers get which content
  • You are preparing a pitch to advertisers or sponsors and need to articulate who your audience segments are and why they are valuable

What You Need To Provide

Required: The newsletter's topic and focus; a description of your current audience (who subscribes, what industries or roles they represent, what you know about why they signed up); any available engagement data (even rough — e.g., "about 40% open every edition, another 30% open occasionally").

Optional: Subscriber count; the newsletter's format and frequency; any survey data, reader feedback, or demographic information; the business model (free, freemium, paid, sponsor-supported); specific segmentation goals (e.g., "I want to identify who would pay for a premium tier").

How the Assistant Approaches This

  1. Analyzes the audience signals. Reviews all provided information — topic, engagement data, reader feedback, stated demographics — and identifies the natural fault lines in the audience. These are the characteristics along which subscribers differ meaningfully: their expertise level, their primary use case for the content, their engagement pattern, or their professional context.

  2. Defines 3-5 segments with clear boundaries. Each segment gets a descriptive label, a one-paragraph profile, an estimated share of the audience (based on the data provided or reasonable inference), and the defining characteristic that separates it from adjacent segments. Segments are mutually exclusive — a subscriber belongs to one primary segment.

Read the full file on GitHub · 142 lines

Files

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.

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. 8d ago First seen · 142 lines · 36 tokens per session scan A 31235d31fe20

Subscribe to this mod's changes

newsletter-audience-segmenter is a skill published in the GitHub repository ur-grue/autopunk-media-skills (32 stars, last pushed 12d ago), licensed MIT. It adds 36 tokens to every session and 2,569 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-09-04.