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 jonathimer/devmarketing-skills --skill developer-churngit clone --depth 1 https://github.com/jonathimer/devmarketing-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/jonathimer/devmarketing-skills/developer-churn)<a href="https://agentmods.dev/skills/jonathimer/devmarketing-skills/developer-churn"><img src="https://agentmods.dev/badge/skills/jonathimer/devmarketing-skills/developer-churn/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/jonathimer/devmarketing-skills/developer-churn"><img src="https://agentmods.dev/badge/skills/jonathimer/devmarketing-skills/developer-churn.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.00057 | $0.03775 |
| Opus 5.5 | $0.00023 | $0.01510 |
| Sonnet 5.5 | $0.00011 | $0.00755 |
| Haiku 4.5 | $0.00006 | $0.00378 |
Grade A, and why
developer-churn 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 1mo 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 — 638 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Churn
This skill helps you understand why developers leave, identify at-risk users before they churn, and win back those who've already left. No guilt trips or desperate discounts — just honest understanding and genuine value.
Before You Start
-
Load your developer audience context:
- Check if
.agents/developer-audience-context.mdexists - If not, run the
developer-audience-contextskill first - Understanding your developers' alternatives and pain points is critical for churn analysis
- Check if
-
Gather your data:
- Current churn rate by segment
- Most recent churned users (last 30-90 days)
- Support ticket history for churned users
- Usage patterns before churn
- Exit survey data (if any)
Understanding Developer Churn
Developer churn is different from typical SaaS churn:
| Consumer/SMB SaaS | Developer Tools |
|---|---|
| Price sensitivity high | Value sensitivity high |
| Features drive decisions | DX drives decisions |
| Support tickets = engagement | Support tickets = friction |
| Monthly churn cycles | Project-based churn |
| Competitor marketing works | Peer recommendations work |
Key insight: Developers don't leave because of price. They leave because of friction, frustration, or finding something better.
The 6 Reasons Developers Churn
1. Developer Experience (DX) Issues
Symptoms:
- High time-to-first-value
- Frequent support tickets on basic tasks
- Complaints about docs or SDKs
- "It's too complicated" feedback
Root causes:
- Poor documentation
- Buggy SDKs
- Breaking changes without migration paths
- Confusing authentication
- Missing quickstarts
Detection signals:
- Support tickets mentioning "confused" or "doesn't work"
- High signup-to-activation drop-off
- Long time between signup and first API call
- Multiple failed API calls before success
2. Pricing and Billing Friction
Symptoms:
- Downgrades before cancellation
- Usage dropping to stay under limits
- Questions about billing
- Requests for enterprise/custom pricing
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.
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.
- 1mo ago First seen · 638 lines · 57 tokens per session scan A b6bf1ba2627a
developer-churn is a skill published in the GitHub repository jonathimer/devmarketing-skills (87 stars, last pushed 7mo ago), licensed MIT. It adds 57 tokens to every session and 3,775 once invoked, about $0.0002 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-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.