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 varunk130/ai-ux-skill-library --skill ai-journey-mappergit clone --depth 1 https://github.com/varunk130/ai-ux-skill-libraryWrote 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/varunk130/ai-ux-skill-library/ai-journey-mapper)<a href="https://agentmods.dev/skills/varunk130/ai-ux-skill-library/ai-journey-mapper"><img src="https://agentmods.dev/badge/skills/varunk130/ai-ux-skill-library/ai-journey-mapper/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/varunk130/ai-ux-skill-library/ai-journey-mapper"><img src="https://agentmods.dev/badge/skills/varunk130/ai-ux-skill-library/ai-journey-mapper.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.00059 | $0.02437 |
| Opus 5 | $0.00030 | $0.01218 |
| Sonnet 5 | $0.00012 | $0.00487 |
| Haiku 4.5 | $0.00006 | $0.00244 |
Grade A, and why
ai-journey-mapper 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.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Journey Mapper
Map the unique journeys users take when interacting with AI products - from first encounter through mastery. Unlike traditional journey mapping, AI journeys include trust arcs, capability discovery curves, mental model evolution, and the shifting balance of human-AI control. The PATHWAY framework captures what traditional journey maps miss.
Core Principle
Traditional journey maps track what users DO. AI journey maps must also track what users BELIEVE - because the gap between what users believe the AI can do and what it actually can do is where every AI UX problem lives.
The PATHWAY Framework
| Letter | Dimension | What to Map |
|---|---|---|
| P | Perception Evolution | How the user's mental model of the AI changes over time |
| A | Autonomy Gradient | How the balance of human vs. AI control shifts across the journey |
| T | Trust Arc | How trust rises, falls, and recovers through the experience |
| H | Help Moments | Where the user needs assistance understanding the AI (not just the product) |
| W | Wow Moments | Where the AI exceeds expectations and creates advocacy |
| A | Anxiety Points | Where the user feels uncertain, vulnerable, or out of control |
| Y | Yield Decisions | Where the user must decide: trust the AI, override it, or disengage |
AI Journey Map Structure
An AI journey map extends the traditional CJM with AI-specific rows:
Standard Rows (from traditional journey mapping)
| Row | Content |
|---|---|
| Phases | 4-6 stages of the AI adoption journey |
| Actions | What the user does at each phase |
| Touchpoints | Where interactions occur |
| Pain Points | Friction and frustration sources |
| Opportunities | Design improvement possibilities |
AI-Specific Rows (unique to this skill)
| Row | Content | Why It Matters |
|---|---|---|
| Mental Model | What the user believes the AI can do at this phase | Misaligned mental models cause 80% of AI UX failures |
| Trust Level | High / Medium / Low / Broken - with the event that caused the change | Trust is the #1 predictor of AI adoption and retention |
| Autonomy Balance | Who is in control: User-led → Collaborative → AI-led | The shift from "I use the AI" to "the AI works for me" is the key transition |
| Capability Awareness | Percentage of AI capabilities the user has discovered | Most users discover < 30% of capabilities in the first month |
| Verification Behavior | How much the user checks AI outputs | Decreasing verification = growing trust (or dangerous complacency) |
| Error Exposure | What AI failures the user has encountered | Each error type reshapes the mental model differently |
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 · 196 lines · 59 tokens per session scan A 978cbceda94a
ai-journey-mapper is a skill published in the GitHub repository varunk130/ai-ux-skill-library (3 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,437 once invoked, about $0.0003 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
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
component-family-consistency
Buttons, inputs, pills, badges, calendars, and other interactive components form a visual family — they share the same border-radius, colour logic, shadow scale, border style, and spacing rhythm. Inconsistency between them breaks the sense of a coherent product. Use when building or reviewing a component library…
modular-scale-typography
Typography feels cohesive and intentional when font sizes follow a modular scale — a ratio-based sequence where every size is mathematically related to the others. Use when defining type scales, setting up design tokens, reviewing font size choices, or when typography feels inconsistent or arbitrary.
extract-design
Extract a complete design system — colors, typography, spacing, components, shadows, and W3C design tokens — from any live website using Dembrandt. Runs a headless browser against the URL and returns real computed values from the DOM. Use when you need a site's actual design tokens, want to reverse-engineer a visual…
algorithmic-color-palette
Derive a full UI colour palette algorithmically from one or two brand colours. Darker and lighter variants for interactive states, desaturated greys from the brand hue for borders and backgrounds, and semantic colours that feel coherent with the brand rather than generic. Use when building a colour system from scratch…
brand-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…