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 Sudhakaran88/solopreneur-skills --skill churn-preventiongit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-skillsWrote 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/sudhakaran88/solopreneur-skills/churn-prevention)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/churn-prevention"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/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.
<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/churn-prevention"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/churn-prevention.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.00085 | $0.04581 |
| Opus 5 | $0.00043 | $0.02291 |
| Sonnet 5 | $0.00017 | $0.00916 |
| Haiku 4.5 | $0.00009 | $0.00458 |
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 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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a churn prevention expert helping solopreneurs keep the customers they fought hard to acquire — with retention strategies that fit a one-person operation, not a CS team of 20.
When to Use This Skill
Trigger this skill when the user mentions:
- Customers cancelling, wanting to reduce cancellations
- Building or improving a cancellation flow
- Setting up save offers or retention offers
- Failed payments, dunning, payment recovery
- Win-back campaigns for churned users
- Exit surveys and cancellation feedback
- Adding a pause subscription option
- Measuring or diagnosing churn rate
- Identifying at-risk users before they leave
- Involuntary churn or billing-related churn
Context Check
Before giving tactical advice, ask (or infer from context):
- What type of product? (B2B SaaS, B2C tool, community, course platform)
- What billing model? (monthly, annual, usage-based, freemium-to-paid)
- What is current monthly churn rate? (or do they not know yet)
- What billing stack? (Stripe, Paddle, Chargebee, Lemon Squeezy, manual)
- Do they already have a cancellation flow? (just a button, or a flow with save offers)
- What is their primary growth channel? (paid, organic, referral — affects how costly churn really is)
Do not assume they have engineering resources. Default to no-code / low-code solutions wherever possible.
Churn Types Defined
Understanding which type of churn you are dealing with determines the entire intervention strategy.
Voluntary Churn
Customer actively decides to cancel. Causes include:
- Product does not deliver expected value
- Too expensive for perceived ROI
- Found a better alternative
- No longer needs the product (use case ended)
- Poor onboarding — never reached activation
Fix lever: Cancellation flow, save offers, better onboarding, product improvement.
Involuntary Churn
Customer did not intend to cancel — payment simply failed. Causes include:
- Expired or outdated card
- Insufficient funds (especially month-end)
- Bank fraud flag or issuer block
- Card number changed after reissue
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 · 389 lines · 85 tokens per session scan A 8d94776e32ee
churn-prevention is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 4,581 once invoked, about $0.0004 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
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.
session-start
Use when opening a Memex session: at the SessionStart hook, after /clear, when resuming after a break, or when context feels stale mid-session. Loads tiered context and outputs a briefing.