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-journey-mapgit 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-journey-map)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/customer-journey-map"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/customer-journey-map/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-journey-map"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/customer-journey-map.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.00086 | $0.03953 |
| Opus 5.5 | $0.00034 | $0.01581 |
| Sonnet 5.5 | $0.00017 | $0.00791 |
| Haiku 4.5 | $0.00009 | $0.00395 |
Grade A, and why
customer-journey-map 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Habilidad: Mapa de Recorrido del Cliente
Esta habilidad produce un mapa de recorrido del cliente completo que cubre cada etapa, desde la conciencia hasta la defensa. Cada etapa incluye puntos de contacto, acciones del cliente, emociones, puntos de fricción y oportunidades de mejora específicas. El resultado está listo para usar en descubrimiento de productos, diseño UX o talleres de alineación entre funciones.
Entradas Requeridas
Trabaja a partir de lo que se proporciona. Si falta algo, igualmente produce el resultado completo: rellena cada brecha con una suposición razonable marcada (asumido, confirmar) y enumera esas suposiciones al final. Haz una pregunta solo cuando falte el tema central en sí (no hay nada sobre qué escribir).
- Producto o servicio siendo mapeado
- Persona del cliente — ¿para qué segmento de cliente es este mapa? (sé específico — una persona por mapa)
- Alcance del recorrido — de extremo a extremo completo (conciencia → defensa), ¿o una fase específica? (p. ej. solo incorporación)
- ¿Estado actual o estado futuro? — ¿Mapear cómo funciona hoy, o diseñar cómo debería funcionar?
- Fuentes de datos — ¿hay investigación, entrevistas con usuarios, tickets de soporte, comentarios NPS, análisis disponibles?
- Objetivo del mapa — ¿qué decisión informará esto? (rediseño, priorización, alineación de stakeholders, nueva característica)
Estructura de Salida
Mapa de Recorrido del Cliente: [Producto / Servicio]
Persona: [Nombre — p. ej. "María, la gerente de RRHH abrumada"] Alcance del recorrido: [De extremo a extremo completo / Incorporación / Compra / Renovación] Estado actual o futuro deseado: [Estado actual / Estado futuro deseado] Preparado por: [Nombre / Equipo] Fecha: [Fecha] Basado en: [Fuentes de investigación — entrevistas, análisis, datos de soporte, asumido/hipotético]
Resumen de la Persona
| Nombre | [María] |
| Rol | [Gerente de RRHH en una firma de servicios profesionales de 200 personas] |
| Objetivo | [Reducir el tiempo dedicado a la gestión manual de datos de empleados] |
| Frustraciones | [Demasiadas herramientas que no se comunican entre sí; siempre buscando aprobaciones] |
| Comodidad técnica | [Moderada — cómoda con herramientas SaaS pero no una usuaria avanzada] |
| Poder de decisión | [Recomienda herramientas; presupuesto aprobado por la CHRO] |
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 · 243 lines · 86 tokens per session scan A ebd8bfe73ce4
customer-journey-map is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 3,953 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…