mapping-user-journeys

mapping-user-journeys is a skill for Claude Code from Nolane-x/forge-os. It costs 38 tokens per session (1,446 once invoked), scanned A, original, MIT.

A UX-planning skill for laying out the steps a user takes through a product or service. A user journey shows actions, decisions, and possible outcomes from start to finish.

In plain words
What is it for?
Use it to map journeys from a product definition and documented user workflows.
Why use it?
It helps expose gaps, unclear transitions, and missing states in an experience before implementation.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the forgeos plugin — 196 skills, 1 command, 1 agent, 1 MCP server shipped together

Good fit Use it to map journeys from a product definition and documented user workflows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nolane-x/forge-os/mapping-user-journeys
Install

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.

Any agent
npx skills add Nolane-x/forge-os --skill mapping-user-journeys
Clone the repo
git clone --depth 1 https://github.com/Nolane-x/forge-os

Made for: Claude Code.

Or install forgeos, the plugin that ships this one along with the rest of its 196 skills, 1 command, 1 agent, 1 MCP server.

Wrote 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.

agentmods badge for mapping-user-journeys

README.md
[![agentmods](https://agentmods.dev/badge/skills/nolane-x/forge-os/mapping-user-journeys/github.svg)](https://agentmods.dev/skills/nolane-x/forge-os/mapping-user-journeys)
Your own site
<a href="https://agentmods.dev/skills/nolane-x/forge-os/mapping-user-journeys"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/mapping-user-journeys/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.

agentmods 80×15 button for mapping-user-journeys

Your own site · 80×15
<a href="https://agentmods.dev/skills/nolane-x/forge-os/mapping-user-journeys"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/mapping-user-journeys.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,446 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01446
Opus 5 $0.00019 $0.00723
Sonnet 5 $0.00008 $0.00289
Haiku 4.5 $0.00004 $0.00145

Measured 5d ago against content hash 9c3521eda986, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

mapping-user-journeys 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 5d 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.

skills/core/ux/mapping-user-journeys/SKILL.md · 134 lines

How it starts

The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mapping User Journeys

Overview

This skill owns one bounded responsibility: mapping user journeys. Its focus is mapping user journeys within ux lifecycle boundaries. It converts declared inputs into typed artifacts and reproducible evidence without silently changing product scope.

Trigger

Activate only when the project is in one of these stages: ux-design, all contract preconditions pass, and the router identifies a missing output this skill can produce. Do not activate merely because the skill name resembles the user request.

Required Inputs

  • product-definition
  • user-workflows
  • Current gate result, open findings, artifact hashes, and invalidation state
  • Required tools: none
  • Optional tools: none
  • Confirmed human decisions relevant to this scope

Method-Specific Protocol

  1. Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by mapping user journeys.
  2. Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to mapping user journeys.
  3. Apply mapping user journeys only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required.
  4. Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers.
  5. Create reproducible checks that would fail if mapping user journeys were incomplete or implemented incorrectly.

Procedure

  1. Read user workflows, constraints, devices, and accessibility needs.
  2. Define critical journeys and failure recovery before visual styling.
  3. Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by mapping user journeys.
  4. Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to mapping user journeys.
  5. Apply mapping user journeys only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required.
  6. Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers.
  7. Create reproducible checks that would fail if mapping user journeys were incomplete or implemented incorrectly.
  8. Specify interaction states, information hierarchy, and feedback.
  9. Create responsive and accessible behavior contracts.
  10. Validate critical flows against realistic user tasks.
  11. Publish UI evidence, open questions, and handoff contracts.

Read the full file on GitHub · 134 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 5d ago First seen · 134 lines · 38 tokens per session scan A 9c3521eda986

Subscribe to this mod's changes

mapping-user-journeys is a skill published in the GitHub repository Nolane-x/forge-os (10 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,446 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-09-03.

Related

Other skills, from other repositories

brand-identity

Define brand strategy, voice, visual direction, tagline, and usage guidelines. Use when creating, refreshing, or standardizing a product or company brand.

aAAaqwq/AGI-Super-Team · 34 tokens

canva-automation

Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas.

aAAaqwq/AGI-Super-Team · 38 tokens

content-typography

A Chinese-language typography and layout guide for content images such as social-media covers, article headers, and posters. It covers headline wording, line breaks, hierarchy, font weight, alignment, spacing, and platform fit.

aAAaqwq/AGI-Super-Team · 128 tokens

code-material-gen

A code-based graphics tool that uses HTML and CSS, then renders the result with Playwright, a browser automation tool. It is designed for Chinese text, selectable fonts, and repeatable layouts.

aAAaqwq/AGI-Super-Team · 75 tokens

fidelity-gate

Build a UI against a frozen visual reference without drift - an inventory extracted before any code, a relics list, and a gate that MEASURES computed styles on a fixture carrying the reference's own data. Use when a mockup, design spec or screenshot is the contract.

jjanczur/tyran · 56 tokens

crossbreed

Structural recombination of existing designs. Takes 2-3 prototypes or design approaches and spawns N agents to create HYBRID designs, each with a different "dominant parent" whose architecture leads while grafting specific elements from the others.

sjarmak/agent-workflows · 0 tokens