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 bromso/metapowers --skill churn-preventiongit clone --depth 1 https://github.com/bromso/metapowersWrote 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/bromso/metapowers/churn-prevention)<a href="https://agentmods.dev/skills/bromso/metapowers/churn-prevention"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/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/bromso/metapowers/churn-prevention"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/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.00067 | $0.00739 |
| Opus 5.5 | $0.00027 | $0.00296 |
| Sonnet 5.5 | $0.00013 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
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 3d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Churn Prevention
Analyze and reduce churn for "$ARGUMENTS". Identify churn signals, design interventions, and build retention strategies.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .metapowers/marketing/<project>/skip-log.md: - <ISO timestamp> — <skill name> skipped prerequisite check for <artifact file> — reason: <reason or "none given">.
Prerequisites
Read .metapowers/marketing/<project>/00-strategy.md. If this file does not exist, tell the user:
Phase 0 (Strategy) has not been completed for "". Run
/marketing:customer-research <project>first, or use--skip-checksto bypass.
Process
-
Read context:
- Read
.metapowers/marketing/<project>/00-strategy.mdfor audience and product context - Read
.metapowers/marketing/<project>/04-engage.mdif it exists
- Read
-
Identify churn signals:
- Usage decline patterns (login frequency, feature usage drop)
- Support ticket patterns that precede churn
- Billing signals (failed payments, downgrade inquiries)
- Engagement signals (email opens dropping, NPS decline)
-
Analyze churn reasons:
- Use WebSearch to find common churn reasons in the category
- Map reasons to: product gaps, pricing issues, poor onboarding, competitive switching, need ended
- Which reasons are preventable vs. natural?
-
Design interventions:
- Early warning system: automated alerts on churn signals
- Re-engagement campaigns: email, in-app, personal outreach
- Cancellation flow optimization: save offers, feedback collection, easy pause option
- Win-back campaigns: timing, messaging, incentives
- Product improvements that address top churn reasons
-
Write the artifact — append to
.metapowers/marketing/<project>/04-engage.mdunder a## Churn Preventionsection. Create the file with a# Engage — <project>heading if it does not exist; if a## Churn Preventionsection already exists, replace only that section. The section contains:- Churn Signals — early warning indicators to monitor
- Churn Reasons Analysis — categorized and prioritized
- Intervention Playbook — action per signal/reason
- Cancellation Flow Design — save offers and feedback
- Win-Back Campaign — timing and messaging
- Retention Metrics — what to track
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.
- 3d ago First seen · 57 lines · 67 tokens per session scan A b44b12f8627b
churn-prevention is a skill published in the GitHub repository bromso/metapowers (2 stars, last pushed 3d ago), licensed MIT. It adds 67 tokens to every session and 739 once invoked, about $0.0003 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-10-21.
Other skills, from other repositories
design-method
Use when starting any design task — resolves register, sets the 3 dials, locks Gate 0, and routes to the right move and target skill.
design-webapp
Use when building or extending a dashboard, SaaS screen, or any authenticated app surface — use design-web instead for a marketing site.
react-tanstack-router
Use when implementing routing in a React app (NOT Next.js) with TanStack Router — file-based routes, loaders, search params.
fusecore
Use when creating modules, understanding FuseCore structure, or implementing features in a FuseCore modular-monolith Laravel project.
laravel-billing
Use when implementing subscriptions, invoices, payment methods, webhooks, or billing portals with Laravel Cashier (Stripe or Paddle).
laravel-permission
Use when implementing RBAC, role-based access control, or user authorization with Spatie Laravel Permission.