What is user-flow-maps?

A tool for turning screens, user actions, decisions, branches, and failure paths into visual flow diagrams. It creates self-contained HTML files that can be opened directly from disk.

Use it to document user journeys, map application screens, show decision paths, and give reviewers a visual version of acceptance criteria.

It makes screen-to-screen behaviour easier to review than a text description. Automatic layout keeps arrows, labels, and branches organized as the flow changes.

user-flow-maps — Skill for Claude Code by arozumenko

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 arozumenko/sdlc-skills --skill user-flow-maps

Clone the repo

git clone --depth 1 https://github.com/arozumenko/sdlc-skills

Made for: Claude Code.

Or install sdlc-skills, the plugin that ships this one along with the rest of its 53 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/user-flow-maps/github.svg)](https://agentmods.dev/skills/arozumenko/sdlc-skills/user-flow-maps)

Your own site

<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/user-flow-maps"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/user-flow-maps/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/user-flow-maps"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/user-flow-maps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 175 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,400 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00175	$0.01400
Opus 5	$0.00088	$0.00700
Sonnet 5	$0.00035	$0.00280
Haiku 4.5	$0.00017	$0.00140

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

Security

Grade A, and why

user-flow-maps 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 9d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/build-flowmaps.mjs, scripts/flowmap.js, scripts/story.test.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

bundles/feature-development/skills/user-flow-maps/SKILL.md · 104 lines

How it starts

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

User-flow maps

Turn a flow — screens, decisions, branches, failure paths — into a reviewable HTML poster. The output is one self-contained file per flow plus an index that links them; it opens straight from disk, no server and no network.

The one rule

You supply data. The library supplies every coordinate.

Hand-positioning a flow map is a trap: it looks fine until an edge is added, then captions collide, arrows point into empty space, and each fix creates the next one. scripts/flowmap.js owns layout, lane packing, orthogonal routing, anchor selection and label de-collision. Never write pixel maths in a spec.

Workflow

Write a spec. One JSON file describing the whole set. See references/spec-schema.md for the contract and a worked example.
Build.
```
node scripts/build-flowmaps.mjs <spec.json> --out <dir>
```
Add --layout story [--screens <dir|file>] to build into a shared design-story site instead of a standalone set: pages land in <out>/flows/<slug>.html (one directory deeper than the flat default) so they can sit next to screen-specs' screens/ output without a filename collision. When --screens points at the matching *.screens.json spec(s), every flow node whose id matches a screen's node becomes a click-through to that screen's page (../screens/<slug>.html#<screenId>). Omitting --screens (or pointing it at nothing yet built) just renders the flow with no screen links — this build never depends on the other having run first.
Verify before you claim it works. Open the pages and check them — the library is deterministic but a spec can still describe a flow badly (a dangling target, a decision with no outcomes). references/verifying.md has a copy-paste browser audit that reports edge/caption collisions, overlapping labels and orphan nodes. Run it. A flow map that looks drawn but routes an arrow through a screen is worse than no diagram.

How ids drive layout

Read the full file on GitHub · 104 lines

Files

What ships with it

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

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.

9d ago First seen · 104 lines · 175 tokens per session scan A f4e16b1cf4c2

Subscribe to this mod's changes

user-flow-maps is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed 5d ago), licensed MIT. It adds 175 tokens to every session and 1,400 once invoked, about $0.0009 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-30.

Design and UX

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.

nexu-io/open-design · 41 tokens

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.

nexu-io/open-design · 53 tokens

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

nexu-io/open-design · 78 tokens

user-flow-maps