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 uthumany/uthy-legacy-os --skill churn-analysisgit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/churn-analysis)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/churn-analysis"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/churn-analysis/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/uthumany/uthy-legacy-os/churn-analysis"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/churn-analysis.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.00030 | $0.00913 |
| Opus 5.5 | $0.00012 | $0.00365 |
| Sonnet 5.5 | $0.00006 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
churn-analysis 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 2mo 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Churn Analysis
Overview
Churn is the silent killer of product growth. Losing 5% of users per month means losing 46% per year — you'd need 50%+ annual growth just to stay flat. This skill helps you diagnose why users leave, identify leading indicators of churn, and design retention interventions.
When to Use
- Monthly or quarterly churn is above target
- You need to understand WHY users are leaving
- You're designing retention campaigns or reactivation flows
- Building a churn prediction model
- Don't use for: one-off cancellations (talk to the user directly), products with < 100 active users (too few data points)
Instructions
1. Measure Churn Correctly
Definition: Users who stop using your product within a given period.
- User churn: % of users who stop using
- Revenue churn: % of recurring revenue lost (often different from user churn)
- Gross churn: Total lost (include downgrades and cancellations)
- Net churn: Lost - expansions (can be negative = negative churn = growth)
Segment churn by:
- Plan: Free vs. paid vs. enterprise
- Cohort: Users who joined in the same month
- Behavior: Heavy vs. light users
- Source: How were they acquired?
2. Find Leading Indicators
Churn doesn't happen overnight. Look for early warning signs:
- Engagement drop: Frequency of use decreases over 2+ weeks
- Feature decay: Stop using key features
- Support contact: Filing complaints or asking about cancellation
- Billable action stops: For revenue-churn, look for stopped billing-related actions
- Account changes: Team members leaving, admin changing
3. Analyze Churn Reasons
Quantitative:
- Cancel survey results (what did they select?)
- Last actions before churn (what did they do last?)
- Usage patterns of churned vs. retained users
Qualitative:
- Exit interviews: "What made you decide to leave?"
- Win-back conversations: "What would it take to come back?"
- Lost deal analysis: "Why did you choose competitor X?"
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.
- 2mo ago First seen · 99 lines · 30 tokens per session scan A e88659215080
churn-analysis is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 913 once invoked, about $0.0001 per session on Opus 5.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.
churn-analysis compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| churn-analysisuthumany/uthy-legacy-os | Skill | 5 | 5mo ago | MIT | A | 30 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |