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.
npx agentmods add commands/alwkala/tidyfactor-design/flowgit clone --depth 1 https://github.com/alwkala/tidyfactor-designWhat 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 | $0.00000 | $0.00480 |
| Opus 5 | $0.00000 | $0.00240 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
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 3d 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 — 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
- Map the intended user journeys from the brief (e.g. landing → pricing → signup → dashboard-overview) — real navigation intent, not just "link everything to everything".
- 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. - 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. - 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. - 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
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.
- 3d ago First seen · 45 lines · 0 tokens per session scan A d7b78324f7b0
flow is a command published in the GitHub repository alwkala/tidyfactor-design (5 stars, last pushed 1mo 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.
Other commands, from other repositories
github-issue
Create a GitHub issue from a natural language description.
test
Hello world test command.
coograph-verify
Verify that the described work is complete and correct. Provide evidence for every claim. You verify — you do not implement or fix style.
map
Generate a token-budgeted map of the codebase for LLM session bootstrap.
commit-message
Generate a conventional commit message from staged changes.
pr-description
Generate a PR title and description from the current branch diff against main.