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 exiao/pm-skills --skill journey-mappinggit clone --depth 1 https://github.com/exiao/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/exiao/pm-skills/journey-mapping)<a href="https://agentmods.dev/skills/exiao/pm-skills/journey-mapping"><img src="https://agentmods.dev/badge/skills/exiao/pm-skills/journey-mapping/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/exiao/pm-skills/journey-mapping"><img src="https://agentmods.dev/badge/skills/exiao/pm-skills/journey-mapping.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.00128 | $0.01585 |
| Opus 5 | $0.00064 | $0.00792 |
| Sonnet 5 | $0.00026 | $0.00317 |
| Haiku 4.5 | $0.00013 | $0.00159 |
Grade A, and why
journey-mapping 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 10d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
journey-mapping
A journey map is a shared picture of how a person experiences a process over time, from their point of view, not the org's. Its job is not to be pretty. Its job is to (1) create a shared truth a team can point at, and (2) surface the specific moments where the experience breaks so you know where to invest. A map that ends without prioritized opportunities is decoration.
Before you map: scope it
A journey map is only meaningful with a fixed viewpoint. Nail these first, or the map will be a vague average of nobody:
- Persona / actor. ONE specific person type, with goals and context. "Users" is not a persona. If you have research personas, use one; if not, name a concrete archetype and its motivation.
- Scenario + goal. The specific journey and what the person is trying to accomplish ("first-time user setting up the product and reaching first value"). One scenario per map. Onboarding and renewal are different maps.
- Scope boundaries. Where does the journey start and end? Widen too far and it's shallow; narrow too far and you miss the handoffs where experiences usually break.
- Grounding. Is this current-state (what happens today, from evidence) or future-state (the experience you intend to design)? Say which. Current-state maps must be built from real signal (interviews, support tickets, session recordings, analytics, a dogfood pass), not assumptions. If you're assuming, label the assumption rows explicitly so they can be validated.
The anatomy (rows of the map)
Lay stages across the top as columns. For each stage, fill these rows:
- Stage / phase — the chunk of the journey (e.g. Discover → Onboard → First use → Habit → Renew). Name them in the user's language, not the funnel's.
- Actions — what the person actually does in this stage, concrete steps.
- Thoughts / questions — what's going through their head; the questions they need answered to continue. Verbatim quotes if you have them.
- Emotions — the emotional curve across the journey (rising/falling, a plotted line). This is what makes a map more than a flowchart; the low points are where you focus.
- Touchpoints / channels — where the interaction happens (app screen, email, support, physical, third party).
- Pain points — friction, confusion, drop-off, unmet need, moments of doubt. Be specific and locate each at a stage.
- Opportunities — for each pain point, what could fix or improve it. This feeds prioritization.
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.
- 10d ago First seen · 83 lines · 128 tokens per session scan A 772eb485990f
journey-mapping is a skill published in the GitHub repository exiao/pm-skills (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 128 tokens to every session and 1,585 once invoked, about $0.0006 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
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
make-resume
A Chinese-language tool for creating editable HTML resumes that can be changed in a browser and printed to PDF. It uses available resume templates when they are installed and otherwise provides a simpler fallback.