user-flow

A tool that reconstructs the user journey shown in a screen recording as numbered steps with screenshots. A user journey describes the sequence of actions and results a person experiences.

In plain words
What is it for?
Use it to create step-by-step user-flow documents showing navigation, interactions, newly visible elements, and spoken context.
Why use it?
It makes a recorded workflow easier to understand and reuse for documentation, quality checks, or onboarding instructions.

Skill for Claude CodeCodex

Part of the video-insight plugin — 17 skills shipped together

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.

agentmods
npx agentmods add skills/gowtham012/claude-plugins/user-flow
Any agent
npx skills add gowtham012/Claude-plugins --skill user-flow
Clone the repo
git clone --depth 1 https://github.com/gowtham012/Claude-plugins

Made for: Claude Code, Codex.

Or install video-insight, the plugin that ships this one along with the rest of its 17 skills.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 274 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00048 $0.00274
Opus 5 $0.00024 $0.00137
Sonnet 5 $0.00010 $0.00055
Haiku 4.5 $0.00005 $0.00027

Measured 2d ago against content hash c9393fc52c07, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

user-flow 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 2d 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.

video-insight/skills/user-flow/SKILL.md · 33 lines

What it actually says

Generate user flow from video: $ARGUMENTS

Steps

  1. Call MCP tool mcp__video-insight__user_flow with video_path = $0.
  2. Read keyframe image for each step.
  3. Use step.label as the step title, text_appeared for new visible elements, narration for spoken context.
  4. Generate a numbered markdown flow:
## User Flow: <filename>

**Step 1 — Start / Landing** (0s)
[keyframe]
User sees: Dashboard, Analytics, Layers, Wallet

**Step 2 — Navigate → Products** (3.2s)
[keyframe]
User navigates. New elements: Product Catalog, $29/mo

**Step 3 — Interact: Add to Cart** (8.5s)
[keyframe]
User clicks. New element: Cart (1)
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. 2d ago First seen · 33 lines · 48 tokens per session scan A c9393fc52c07

Subscribe to this mod's changes

user-flow is a skill published in the GitHub repository gowtham012/Claude-plugins (5 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 274 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-08-31.