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 frank-luongt/faos-skills-marketplace --skill customer-success-playbookgit clone --depth 1 https://github.com/frank-luongt/faos-skills-marketplaceWrote 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/frank-luongt/faos-skills-marketplace/customer-success-playbook)<a href="https://agentmods.dev/skills/frank-luongt/faos-skills-marketplace/customer-success-playbook"><img src="https://agentmods.dev/badge/skills/frank-luongt/faos-skills-marketplace/customer-success-playbook/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/frank-luongt/faos-skills-marketplace/customer-success-playbook"><img src="https://agentmods.dev/badge/skills/frank-luongt/faos-skills-marketplace/customer-success-playbook.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.00000 | $0.02235 |
| Opus 5 | $0.00000 | $0.01118 |
| Sonnet 5 | $0.00000 | $0.00447 |
| Haiku 4.5 | $0.00000 | $0.00224 |
Grade A, and why
customer-success-playbook 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: customer-success-playbook description: Design onboarding sequences, build customer health scores, analyze churn risk, and plan account expansion. Use when creating CS playbooks, building health scoring models, diagnosing at-risk accounts, or designing renewal strategies. tags: [customer-success, churn, onboarding, retention]
Customer Success Playbook
Comprehensive framework for customer lifecycle management — from onboarding through expansion and renewal. Build health scores, predict churn, design intervention playbooks, and maximize net revenue retention.
Use this skill when
- Designing customer onboarding sequences (30/60/90-day plans)
- Building or refining a customer health scoring model
- Diagnosing at-risk accounts and designing intervention playbooks
- Planning account expansion (upsell/cross-sell motions)
- Structuring Quarterly Business Reviews (QBRs)
- Analyzing churn patterns and leading indicators
- Designing renewal processes
Do not use this skill when
- Handling individual support tickets (use
customer-service-ticket-resolution) - Building support knowledge base articles (use
customer-service-knowledge-base) - Analyzing support metrics only (use
customer-service-support-metrics) - Designing the product itself based on user research (use product skills)
Instructions
- Define lifecycle stages for your customer base.
- Build the health score model using the composite scoring framework.
- Design onboarding playbook with time-to-first-value (TTFV) milestones.
- Set up churn early warning system with trigger-based interventions.
- Create expansion playbook with signal identification and motion templates.
- Structure QBR cadence using the QBR template.
Customer Lifecycle Stages
| Stage | Duration | Key Objective | Primary Metric |
|---|---|---|---|
| Onboarding | Day 0-30 | Achieve first value milestone | Time-to-First-Value (TTFV) |
| Adoption | Day 30-90 | Embed into daily workflow | DAU/WAU ratio, feature breadth |
| Value Realization | Day 90-180 | Prove ROI to stakeholders | ROI documented, NPS score |
| Expansion | Day 180+ | Grow usage and spend | Expansion revenue, seat growth |
| Renewal | 90 days before renewal | Secure renewal commitment | Renewal rate, multi-year conversion |
| At-Risk | Any time | Prevent churn | Health score recovery, save rate |
| Churned | Post-cancellation | Learn and potentially win back | Churn reason analysis, win-back rate |
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 · 244 lines · 0 tokens per session scan A 7eff07965785
customer-success-playbook is a skill published in the GitHub repository frank-luongt/faos-skills-marketplace (33 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,235 tokens. 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
task-observer
Monitors task execution for skill improvement opportunities. Use during ANY multi-step task, agentic workflow, or work session where the agent uses tools and produces deliverables. Captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers in post-task…
resume-tailor
Use when the user has a specific job posting and wants to customize their resume, CV, work document, and/or cover letter for that role. Also use when they say "I'm applying to..." or share a job link.
resume-builder
Use when the user wants to create or update a source work document in resume or CV format, or create a source cover letter from scratch. Triggers on US resumes ("build my resume") and UK/EU-style work CVs ("build my CV", "I need a CV for a UK role", "European CV"). US academic CVs are out of scope. For first-time…
claim-check
Use when the user wants a final truth pass before submitting a resume, CV, cover letter, LinkedIn section, or application package. Also use when they ask whether a draft contains unsupported, inflated, or hallucinated claims.
linkedin-optimizer
Use when the user wants to improve their LinkedIn profile, rewrite their headline, about, or experience sections, or audit individual profile fields.
proof-asset-creator
Use when the user wants to figure out what proof-of-value asset to build — case study, portfolio piece, personal site content, or any artifact that demonstrates their skills to employers. Ideation and scoping only; once an idea is chosen, the user continues in a fresh agent conversation to produce the asset. Triggers…