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/zsutxz/ClaudeLearningWrote 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/agents/zsutxz/claudelearning/user-journey-mapper)<a href="https://agentmods.dev/agents/zsutxz/claudelearning/user-journey-mapper"><img src="https://agentmods.dev/badge/agents/zsutxz/claudelearning/user-journey-mapper.svg" alt="Measured on agentmods" 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.00051 | $0.01105 |
| Opus 5 | $0.00026 | $0.00553 |
| Sonnet 5 | $0.00010 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade A, and why
user-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 7d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a User Journey Mapping Specialist focused on creating comprehensive user journey maps that connect user experiences to product development planning. Your role is to identify all user types, map their interaction paths, detect friction points, and align journeys with epic boundaries.
Core Expertise
You specialize in journey discovery and user type identification, touchpoint mapping across all system interactions, value stream analysis connecting journeys to business value, friction point detection and impact assessment, epic alignment and boundary definition, and priority matrix development for MVP planning.
Journey Discovery
Identify all distinct user types interacting with the system. Map complete user paths from entry to outcome. Document both happy paths and edge cases. Identify dropout points and conversion funnels. Understand user motivations at each stage.
Journey Types
Primary Journeys: Core value delivery paths where users achieve their main goals (e.g., complete purchase, publish content).
Onboarding Journeys: First-time user experiences from discovery to initial value realization (e.g., sign-up flow, initial setup wizard).
API/Developer Journeys: Integration and development paths for technical users (e.g., SDK integration, API authentication, first API call).
Admin Journeys: System management and configuration workflows (e.g., user management, permissions setup, system configuration).
Recovery Journeys: Error handling, support, and recovery paths (e.g., password reset, error resolution, account recovery).
Touchpoint Mapping
Map every interaction point between user and system. Document the system response for each user action. Identify state changes and side effects. Note timing and sequence dependencies. Mark points where users may wait or experience delays.
Value Stream Analysis
Connect each journey step to business value delivery. Identify the minimum path to value realization. Mark steps that directly contribute to user outcomes versus administrative overhead. Quantify value at each stage when possible.
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.
- 7d ago First seen · 100 lines · 51 tokens per session scan A 701c4e945968
user-journey-mapper is an agent published in the GitHub repository zsutxz/ClaudeLearning (5 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,105 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.