PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
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 mohitagw15856/pm-claude-skills --skill customer-success-plangit clone --depth 1 https://github.com/mohitagw15856/pm-claude-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/mohitagw15856/pm-claude-skills/customer-success-plan)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/customer-success-plan"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/customer-success-plan/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/mohitagw15856/pm-claude-skills/customer-success-plan"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/customer-success-plan.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.00080 | $0.03248 |
| Opus 5.5 | $0.00032 | $0.01299 |
| Sonnet 5.5 | $0.00016 | $0.00650 |
| Haiku 4.5 | $0.00008 | $0.00325 |
Grade A, and why
customer-success-plan 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 2d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Plan de Éxito del Cliente
Este skill produce un plan conjunto de éxito del cliente — un documento vivo compartido entre el CSM y el cliente que alinea resultados, hitos y compromisos mutuos. El resultado está listo para coautorizar con el cliente en una llamada de inicio o QBR.
Entradas Requeridas
Trabajar con lo que se proporcione. Si falta alguno de estos elementos, aun así producir el resultado completo: completar cada vacío con una suposición razonable marcada (asumido, confirmar) y listar esas suposiciones al final. Hacer una pregunta solo cuando falta el tema central (no hay nada sobre lo que escribir).
- Nombre de la cuenta e industria
- Producto / plan comprado
- Stakeholders clave — defensor del cliente y comprador económico
- Objetivos empresariales declarados del cliente — ¿por qué compraron? ¿Qué problema están resolviendo?
- Plazo del contrato y fecha de renovación
- Etapa actual de incorporación (cliente nuevo / expansión / post-QBR / pre-renovación)
- Asientos / licencias / uso comprados
- Riesgos conocidos — brechas de adopción, incertidumbre sobre el defensor, prioridades competentes
Estructura del Resultado
Plan de Éxito del Cliente: [Nombre de la Cuenta]
Producto: [Nombre del producto / nivel del plan] Plazo del contrato: [Fecha de inicio → Fecha de renovación] CSM: [Nombre] Defensor del cliente: [Nombre, Cargo] Patrocinador ejecutivo del cliente: [Nombre, Cargo — si se conoce] Última actualización: [Fecha] Estado: [Activo / En revisión / Completado]
1. Objetivos de la Asociación
¿Cómo se vería el éxito para [Nombre de la Cuenta] al término del contrato?
[Escribir 2–3 oraciones describiendo el objetivo central del cliente en lenguaje claro — qué están tratando de lograr en su negocio, no qué características están usando.]
Objetivo empresarial principal: [p. ej. Reducir el tiempo de contratación en un 30% en los equipos de ingeniería] Objetivo secundario: [p. ej. Consolidar tres herramientas heredadas en una plataforma, ahorrando £X/año] Declaración de éxito (palabras del cliente): "[Cita directa del defensor sobre cómo se vería el éxito — pedir esto en el inicio]"
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.
- 2d ago First seen · 220 lines · 80 tokens per session scan A 36384adc85bb
customer-success-plan is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 3,248 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-12.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…