tidyfactor-design: Command for Claude Code

.agents/skills/tidyfactor-design/references/commands/flow.md

flow is a command for Claude Code from alwkala/tidyfactor-design. It costs 0 tokens per session (480 once invoked), scanned A, original, MIT.

A command that connects separate web pages into a clickable prototype, similar to a design tool's presentation mode.

In plain words
What is it for?
Use it to link journeys such as landing page to pricing, signup, and dashboard, and to add a development-only toolbar for jumping between pages and previewing page states.
Why use it?
It removes the need to manually open pages or explain the intended journey, so someone can follow the main user paths on their own.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: installed under .agents/ (shared by several agents).

This is alwkala/tidyfactor-design's own configuration. It tells Claude Code how to work on tidyfactor-design itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tidyfactor-design configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alwkala/tidyfactor-design. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/alwkala/tidyfactor-design/main/.agents/skills/tidyfactor-design/references/commands/flow.md
Clone the repo
git clone --depth 1 https://github.com/alwkala/tidyfactor-design

Made for: Claude Code.

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 flow

README.md
[![agentmods](https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/flow/github.svg)](https://agentmods.dev/commands/alwkala/tidyfactor-design/flow)
Your own site
<a href="https://agentmods.dev/commands/alwkala/tidyfactor-design/flow"><img src="https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/flow/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 flow

Your own site · 80×15
<a href="https://agentmods.dev/commands/alwkala/tidyfactor-design/flow"><img src="https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 480 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.00000 $0.00480
Opus 5.5 $0.00000 $0.00192
Sonnet 5.5 $0.00000 $0.00096
Haiku 4.5 $0.00000 $0.00048

Measured 2mo ago against content hash d7b78324f7b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

.agents/skills/tidyfactor-design/references/commands/flow.md · 45 lines

How it starts

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

Command: flow — Click-Through Prototype Navigation

Purpose

Turns a folder of independent pages into a navigable prototype a client can click through unassisted — the feature that makes this a genuine Figma "present mode" alternative rather than a pile of static mockups.

When to run it

  • Enough pages exist to connect into a coherent path (a few pages minimum — running this on a single page has nothing to connect).
  • User phrasing: "link these pages together", "make this clickable", "prototype the flow from signup to dashboard", flow.

What it does

  1. Map the intended user journeys from the brief (e.g. landing → pricing → signup → dashboard-overview) — real navigation intent, not just "link everything to everything".
  2. Wire real <a href="..."> links between pages for the primary journeys — this must work with plain static hosting/file:// browsing, not just the dev server.
  3. Add the shared, dev-only prototype toolbar (proto-nav.js): a small floating control (page jump list, "back to flow start", state toggles for pages that expose empty/loading/error states) — visibly styled as a tool, not part of the design itself, and easy to strip out before any production handoff.
  4. Where a linked page doesn't exist yet, either build it (route to page/ dashboard) or mark it clearly as a stub end-point — never a silent dead link.
  5. For state toggles (e.g. viewing a dashboard's empty vs. populated state without needing separate pages): drive them via a URL query param or the toolbar, documented in that page's markup comment.

Output convention

proto-nav.js            ← shared floating toolbar, all pages include it
pages/*.html               ← real <a href> links for primary journeys

Checklist

  • Primary journeys from the brief are actually clickable end-to-end
  • No silent dead links — every reference either resolves or is a marked stub
  • Prototype toolbar is visually distinct from the design itself
  • Works via plain static file browsing, not only the dev server

Read the full file on GitHub · 45 lines

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. 2mo ago First seen · 45 lines · 0 tokens per session scan A d7b78324f7b0

Subscribe to this mod's changes

flow is a command published in the GitHub repository alwkala/tidyfactor-design (6 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 480 tokens. 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.

Related

flow compared with commands from other repositories

flow next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
flowalwkala/tidyfactor-designCommand63mo agoMITA0Claude Code
responsive-auditOwl-Listener/designer-skillsCommand3.3k2mo agoMITA20Claude Code
start-hereOwl-Listener/designer-skillsCommand3.3k2mo agoMITA33Claude Code
critique-screenOwl-Listener/designer-skillsCommand3.3k2mo agoMITA16Claude Code
critique-uxOwl-Listener/designer-skillsCommand3.3k2mo agoMITA26Claude Code
design-formOwl-Listener/designer-skillsCommand3.3k2mo agoMITA22Claude Code
platform-auditOwl-Listener/designer-skillsCommand3.3k2mo agoMITA22Claude Code