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.
git clone --depth 1 https://github.com/lucasgaravelli/pm-skills-claude-codeWrote 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/commands/lucasgaravelli/pm-skills-claude-code/customer-journey)<a href="https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/customer-journey"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/customer-journey/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/commands/lucasgaravelli/pm-skills-claude-code/customer-journey"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/customer-journey.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.05066 |
| Opus 5 | $0.00000 | $0.02533 |
| Sonnet 5 | $0.00000 | $0.01013 |
| Haiku 4.5 | $0.00000 | $0.00507 |
Grade A, and why
customer-journey 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 11d 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.
This is a copy
100% identical to customer-journey — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 589 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/customer-journey
O que essa skill faz
Gera um mapa completo de jornada do cliente em 7 estágios (Awareness → Advocacy), documentando touchpoints, ações, emoções, pain points e oportunidades em cada fase. Identifica momentos críticos: Aha Moment, Moments of Truth e Churn Triggers.
Saída: Customer Journey Map em tabela + análise de momentos críticos + recomendações priorizadas.
Quando usar
- Está mapeando a experiência completa de um segmento de usuário pela primeira vez
- Quer identificar onde usuários abandonam o produto (churn triggers)
- Precisa alinhar múltiplos times (Marketing, Produto, CS, Sales) sobre a experiência do cliente
- Quer priorizar melhorias com base em impacto na jornada, não em opinião
- Está redesenhando onboarding, retenção ou expansion e precisa do contexto completo
Input esperado
Mínimo:
- Produto/serviço: O que o cliente está usando
- Persona: Quem está percorrendo essa jornada (cargo, contexto, objetivo)
- Escopo: Jornada completa ou foco em estágios específicos
Opcional:
- Dados de analytics (funil, retenção, NPS por estágio)
- Trechos de entrevistas com usuários
- Mapa de touchpoints existente
- Métricas de conversão entre estágios
- Tickets de suporte categorizados por estágio
- Personas já definidas (usar /persona se não existir)
Processo
-
Definir a persona — Quem está viajando essa jornada? Se não tem persona definida, criar um perfil mínimo (nome, cargo, contexto, objetivo principal). A jornada muda drasticamente entre personas — nunca mapeie "o usuário genérico".
-
Mapear os 7 estágios com touchpoints — Para cada estágio (Awareness → Consideration → Acquisition → Onboarding → Engagement → Retention → Advocacy), listar os touchpoints onde o usuário interage com produto, marca ou time. Incluir touchpoints offline e de terceiros.
-
Documentar ações, pensamentos e emoções — Por estágio, registrar: o que o usuário FAZ (ações observáveis), o que PENSA (perguntas, dúvidas, expectativas) e o que SENTE (emoção dominante, intensidade 1-5). Basear em dados reais quando possível.
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.
- 11d ago First seen · 589 lines · 0 tokens per session scan A 1d459f7650eb
customer-journey is a command published in the GitHub repository lucasgaravelli/pm-skills-claude-code (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,066 tokens. A static security scan graded it A with 0 findings. It is 100% identical to customer-journey, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.