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 unixcrh/phuryn-pm-skills --skill customer-journey-mapgit clone --depth 1 https://github.com/unixcrh/phuryn-pm-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/unixcrh/phuryn-pm-skills/customer-journey-map)<a href="https://agentmods.dev/skills/unixcrh/phuryn-pm-skills/customer-journey-map"><img src="https://agentmods.dev/badge/skills/unixcrh/phuryn-pm-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/unixcrh/phuryn-pm-skills/customer-journey-map"><img src="https://agentmods.dev/badge/skills/unixcrh/phuryn-pm-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.00049 | $0.00753 |
| Opus 5 | $0.00024 | $0.00377 |
| Sonnet 5 | $0.00010 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00075 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- customer-journey-map — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Journey Map
Map the end-to-end customer experience from awareness through advocacy, identifying emotions, pain points, and improvement opportunities at each stage.
Context
You are creating a customer journey map for $ARGUMENTS.
If the user provides files (interview transcripts, survey data, analytics, support tickets, or existing journey maps), read them first. Use web search to understand the product if a URL is provided.
Instructions
-
Define the persona: Who is traveling this journey? Use a specific persona with JTBD, not a generic user.
-
Map the journey stages (adapt to the product):
Stage Description Awareness How do they first learn about the product? Consideration What do they evaluate? What alternatives do they compare? Acquisition How do they sign up or purchase? Onboarding First experience with the product — time to value Engagement Regular usage — building habits Retention What keeps them coming back? What might cause churn? Advocacy When and why do they recommend the product to others? -
For each stage, document:
- Touchpoints: Where the user interacts with the product, brand, or team (website, email, in-app, support, social media)
- User actions: What they do at this stage
- Thoughts & questions: What's on their mind ("Is this worth my time?" "How do I...?")
- Emotions: How they feel (excited, confused, frustrated, delighted) — rate on a scale or use emoji indicators
- Pain points: Friction, confusion, drop-off risks
- Opportunities: How to improve the experience at this point
-
Identify critical moments:
- Aha moment: When the user first experiences core value
- Moments of truth: Decision points where they commit or abandon
- Churn triggers: Where users most commonly drop off
-
Create the journey map table:
Stage Touchpoint User Action Emotion Pain Point Opportunity
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 · 66 lines · 49 tokens per session scan A 656c0e16318b
customer-journey-map is a skill published in the GitHub repository unixcrh/phuryn-pm-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 49 tokens to every session and 753 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…