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 bjorn-ingmanson/thefroject-plugins --skill customer-success-guidegit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/customer-success-guide)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/customer-success-guide"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/customer-success-guide/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/bjorn-ingmanson/thefroject-plugins/customer-success-guide"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/customer-success-guide.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.00035 | $0.01561 |
| Opus 5 | $0.00017 | $0.00781 |
| Sonnet 5 | $0.00007 | $0.00312 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
customer-success-guide 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Success Guide
Build systems that keep customers successful and growing. Drive outcomes before the customer asks for help, using health scores and lifecycle playbooks to trigger action.
Customer Lifecycle Framework
Every customer moves through these stages. Map playbooks and health indicators to each:
[Closed Won] → Onboarding → First Value → Adoption → Steady State → Expansion → Renewal
Stage Definitions
| Stage | Duration | Success Criteria | Risk If Stalled |
|---|---|---|---|
| Onboarding | 0-30 days | Core setup complete, key users trained | Buyer's remorse, early churn |
| First Value | 30-60 days | Customer achieves their stated primary goal | Abandonment, support escalation |
| Adoption | 60-120 days | Usage expands beyond initial users/use cases | Flat usage, single-threaded risk |
| Steady State | 120+ days | Consistent usage, positive sentiment, low support | Complacency, competitor vulnerability |
| Expansion | Any | Customer sees value in additional products/seats | Missed revenue opportunity |
| Renewal | 90 days pre-renewal | Decision maker engaged, value documented | Churn or downgrade |
Health Score Model
Build a composite health score from leading indicators. Weight signals by their predictive power for renewal:
Signal Categories
| Signal | Weight | Data Source | Green (Healthy) | Yellow (At Risk) | Red (Critical) |
|---|---|---|---|---|---|
| Product usage | 30% | Analytics | Above median for segment | Declining >20% MoM | Below 25th percentile or no login 14+ days |
| Engagement | 25% | CRM, email | Responds to outreach, attends calls | Slow responses, declines meetings | Unresponsive for 30+ days |
| Support | 20% | Ticketing | Low volume, high satisfaction | Increasing volume or escalations | Unresolved P1, executive complaint |
| Sentiment | 15% | NPS, calls | NPS 8+, positive call notes | NPS 6-7, neutral/mixed signals | NPS 0-5, negative feedback, complaints |
| Contract | 10% | CRM | Multi-year, expanding | Single year, flat | Month-to-month, downgraded, overdue payment |
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.
- 10d ago First seen · 139 lines · 35 tokens per session scan A db3f1b3b0e6f
customer-success-guide is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,561 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…