churn-prevention

churn-prevention is a skill for Claude Code from bjorn-ingmanson/thefroject-plugins. It costs 41 tokens per session (707 once invoked), scanned A, original, MIT.

A set of methods for reducing the number of customers who cancel a subscription. It covers cancellation flows, offers to retain customers, win-back campaigns, payment recovery, and retention analysis.

In plain words
What is it for?
Use it to design cancellation and payment-recovery flows, create campaigns for former customers, and analyse subscription churn.
Why use it?
It helps identify why customers leave and choose a suitable response, including pricing changes, re-engagement, support, or failed-payment recovery.

Skill for Claude Code

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

Part of the thefroject-customer-success plugin — 47 skills, 11 commands shipped together

Good fit Use it to design cancellation and payment-recovery flows, create campaigns for former customers, and analyse subscription churn.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bjorn-ingmanson/thefroject-plugins/churn-prevention
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 bjorn-ingmanson/thefroject-plugins --skill churn-prevention
Clone the repo
git clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-plugins

Made for: Claude Code.

Or install thefroject-customer-success, the plugin that ships this one along with the rest of its 47 skills, 11 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.

agentmods badge for churn-prevention

README.md
[![agentmods](https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/churn-prevention/github.svg)](https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/churn-prevention)
Your own site
<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/churn-prevention"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/churn-prevention/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 churn-prevention

Your own site · 80×15
<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/churn-prevention"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/churn-prevention.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 707 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00707
Opus 5 $0.00020 $0.00353
Sonnet 5 $0.00008 $0.00141
Haiku 4.5 $0.00004 $0.00071

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

Security

Grade A, and why

churn-prevention 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.

customer-success/skills/churn-prevention/SKILL.md · 81 lines

How it starts

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

Churn Prevention

You are a retention and churn prevention specialist.

Gather Context First

Check context/ files for product and metrics. Ask only for what's missing:

  1. Current churn rate — Monthly and annual if available
  2. Product type — B2B SaaS, B2C subscription, marketplace?
  3. Pricing model — Monthly, annual, usage-based?
  4. Top cancel reasons — Do you know why people leave?
  5. Current cancel flow — What happens when someone tries to cancel?

Churn Diagnosis

Voluntary Churn (user chooses to leave)

Common causes and interventions:

Reason Intervention
"Too expensive" Offer downgrade, pause, or discount
"Not using it enough" Re-engagement campaign, usage tips
"Missing feature" Share roadmap, suggest workaround
"Switching to competitor" Competitive save offer, highlight switching cost
"Project ended" Pause account, seasonal re-activation
"Bad experience" Escalate to support, personal outreach

Involuntary Churn (payment failure)

Payment failures cause 20-40% of SaaS churn:

  1. Smart retry — Retry at different times/days (Tuesdays convert best)
  2. Pre-dunning — Email before the card expires
  3. Dunning sequence — 3-4 emails over 14 days, escalating urgency
  4. Grace period — Keep access during retry window
  5. Update payment UX — One-click card update, not "log in and go to settings"

Cancel Flow Design

The Ethical Cancel Flow

  1. Ask why — Multiple choice, required (feeds your data)
  2. Offer relevant save — Based on the reason they selected
  3. Confirm clearly — Show what they lose, when access ends
  4. Make it easy — 2-3 clicks max. No calling a phone number.

Save Offer Tiers (based on cancel reason)

  • "Too expensive" → Discount (20-50% for 3 months) or downgrade to cheaper plan
  • "Not using it" → Pause subscription (1-3 months) instead of cancel
  • "Missing feature" → "That's on our roadmap for Q2. Stay and get early access?"
  • Generic → Extend trial / free month

Read the full file on GitHub · 81 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 First seen · 81 lines · 41 tokens per session scan A 08216d1be7b1

Subscribe to this mod's changes

churn-prevention is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 707 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens