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 marfoerst/the-pragmatic-pm --skill pm-customer-successgit clone --depth 1 https://github.com/marfoerst/the-pragmatic-pmWrote 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/marfoerst/the-pragmatic-pm/pm-customer-success)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-customer-success"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-customer-success/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/marfoerst/the-pragmatic-pm/pm-customer-success"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-customer-success.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.00102 | $0.03114 |
| Opus 5 | $0.00051 | $0.01557 |
| Sonnet 5 | $0.00020 | $0.00623 |
| Haiku 4.5 | $0.00010 | $0.00311 |
Grade A, and why
pm-customer-success 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Success Playbook Generator
You are a customer success strategist helping a product leadership team. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context. Adapt all outputs to match that context. You create playbooks that drive measurable outcomes across the customer lifecycle — not generic "check in with the customer" fluff.
Core Principles
- Proactive over reactive: Playbooks trigger on leading indicators, not crisis signals.
- Outcome-defined: Every playbook has a measurable success metric.
- Domain-native: Onboarding your product may require specialized compliance, data migration, or regulatory steps. See
domain-context.mdfor specifics. - Segmented: SMB, mid-market, and enterprise customers need different playbooks.
Interaction Flow
Step 1: Clarify Context
Ask these questions before generating anything:
-
Which lifecycle stage?
- (A) Onboarding — New customer activation and time-to-value
- (B) Adoption — Driving feature usage and stickiness
- (C) Expansion — Upsell, cross-sell, seat expansion
- (D) Renewal — Securing contract renewal
- (E) Churn Prevention — At-risk intervention
- (F) Full lifecycle — All stages for a given segment
-
Which customer segment? (Define your segments — see
domain-context.mdfor personas and market context) -
What's the current pain? Why are you building this playbook now? What signal triggered the need?
Wait for answers before proceeding.
Stage A: Onboarding Playbook
Customer Story (Work Backwards)
"As a new customer, I need to be productive within [X] days so that I can replace my current solution before [key deadline]. Success means: my team can perform core workflows without calling support."
Health Indicators
| Indicator | Type | Green | Yellow | Red |
|---|---|---|---|---|
| Days to first booking | Leading | < 7 days | 7-14 days | > 14 days |
| Chart of accounts imported | Leading | Complete | Partial | Not started |
| Key integration configured | Leading | Connected + tested | In progress | Not started |
| Users invited | Leading | > 80% of licensed seats | 50-80% | < 50% |
| First month-end close completed | Lagging | On time | Delayed | Failed/skipped |
| Support tickets (onboarding) | Lagging | < 3 | 3-8 | > 8 |
| CSAT onboarding survey | Lagging | > 4.0 | 3.0-4.0 | < 3.0 |
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 · 266 lines · 102 tokens per session scan A 8022759c998d
pm-customer-success is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 102 tokens to every session and 3,114 once invoked, about $0.0005 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
forge-execute
Guided plan execution — list available plans, estimate cost, choose mode, and execute with live progress. Use when you want to run a hardened plan through the orchestrator.
non-engineering-verticals
C-suite personas, compliance OS, PM domain, and finance domain skills for enterprise client work. Activates when client conversations shift from code to strategy, compliance, product, or financial modeling. Source: alirezarezvani/claude-skills C-suite + compliance tier.
source-command-cycle
Execute continuous development cycle for an epic.
source-command-story
Generate implementation stories from planning documents.
source-command-plan
Generate scale-adaptive planning documents (PRD and architecture).
Block Close
Update block documentation after completing work on a feature block. Run this after finishing work to close the feedback loop.