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 rampstackco/claude-skills --skill journey-mappinggit clone --depth 1 https://github.com/rampstackco/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/rampstackco/claude-skills/journey-mapping)<a href="https://agentmods.dev/skills/rampstackco/claude-skills/journey-mapping"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-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/rampstackco/claude-skills/journey-mapping"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/journey-mapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00131 | $0.02143 |
| Opus 5.5 | $0.00052 | $0.00857 |
| Sonnet 5.5 | $0.00026 | $0.00429 |
| Haiku 4.5 | $0.00013 | $0.00214 |
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 1mo 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journey Mapping
Build journey maps and service blueprints that surface friction, align teams, and identify opportunities. Stack-agnostic. Tool-agnostic.
This skill is for mapping the experience. For testing specific touchpoints, use usability-testing. For broader generative research, use ux-research. For analyzing conversion, use cro-optimization.
When to use
- Departments have different mental models of the customer experience
- Customer experience feels disjointed across touchpoints
- Specific friction or drop-off points need diagnosis
- Strategic planning needs a shared view of the user
- Service design (front-stage and back-stage) needs alignment
- New product or feature needs to be designed in context of broader experience
When NOT to use
- Testing a single touchpoint or page (use
usability-testing) - Generative research before journey mapping (use
ux-research) - Operational process mapping that doesn't involve users
- Funnel optimization (use
cro-optimization)
Required inputs
- Identified user persona or segment to map (one map per segment)
- Existing research and data about that segment
- Cross-functional access (you cannot map back-stage without ops/support/engineering input)
- Time and stakeholder commitment (a real journey map is a project, not an afternoon)
The framework: 3 deliverables
1. Customer journey map
The user-facing view of the experience.
Structure (rows / lanes):
- Phase. The major stages in the journey (e.g., Awareness, Consideration, Onboarding, Activation, Retention, Advocacy). Phases vary by product type.
- Steps. Specific things the user does within each phase.
- Touchpoints. Where the user interacts with the product, brand, or service (web, app, email, support, social, in-person).
- Goals. What the user is trying to accomplish at this step.
- Thoughts. What's going through their mind.
- Emotions. The emotional state (often visualized on a curve).
- Pain points. Where things go wrong, friction, frustration.
- Opportunities. Where the experience could improve.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 251 lines · 131 tokens per session scan A 5d25b07dd3c6
journey-mapping is a skill published in the GitHub repository rampstackco/claude-skills (987 stars, last pushed 4d ago), licensed MIT. It adds 131 tokens to every session and 2,143 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
visual-qa
Runs rigorous visual QA across web, terminal, and paginated surfaces: an Apple HIG-based checklist, paired light/dark captures at phone and desktop widths, screenshot evidence, and a per-item PASS/FAIL verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right or follows the…
frontend
Builds, styles, and polishes anything drawn with HTML, CSS, or SVG: web UI, pages, components, HTML reports rendered to PDF or print, figures, PNG/SVG diagrams, slides, and images for Notion or Slack. Use for any styling, layout, animation, or visual-quality task, or when asked to make something look or feel a certain…
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
ambience-skill
Layer A ambience-and-typographic-motion reference anchored to the react-bits catalog (reactbits.dev). Stacks on any style skill whenever work adds a hero atmosphere, an animated or shader background, a typographic reveal (split, blur, shimmer, typewriter, count-up, marquee), scroll storytelling, or card surface…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…