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 skills add Dragoon0x/taste-skills --skill flow-patternsgit clone --depth 1 https://github.com/Dragoon0x/taste-skillsWrote 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.
[](https://agentmods.dev/skills/dragoon0x/taste-skills/flow-patterns)<a href="https://agentmods.dev/skills/dragoon0x/taste-skills/flow-patterns"><img src="https://agentmods.dev/badge/skills/dragoon0x/taste-skills/flow-patterns/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.
<a href="https://agentmods.dev/skills/dragoon0x/taste-skills/flow-patterns"><img src="https://agentmods.dev/badge/skills/dragoon0x/taste-skills/flow-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00036 | $0.00290 |
| Opus 5.5 | $0.00014 | $0.00116 |
| Sonnet 5.5 | $0.00007 | $0.00058 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
flow-patterns 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.
What it actually says
Flow Patterns
How a product feels over time, not just in a single frame.
How to use
/flow-patternsApply flow design constraints to this conversation.
Constraints
Flow Principles
- MUST ensure the user can answer at any point: where am I, where did I come from, what happens next?
- MUST use the minimum number of steps for the complexity of the action. Not zero steps. The right number.
- MUST design error recovery as part of the flow, not an afterthought
- SHOULD prefer undo over confirmation ("Action completed. Undo?" beats "Are you sure?")
Progressive Disclosure
- MUST show only what's needed now and reveal complexity on demand
- MUST decide at what point "simple" becomes "hiding things"
- SHOULD use contextual actions (show actions where the content is, not in a distant toolbar)
- SHOULD use smart defaults (pre-fill based on context, set the most common option)
Anti-Patterns
- Multi-step flows with no progress indicator
- Asking for information you could have inferred from context
- Dead-end error states with no recovery path
- Mandatory steps that aren't actually required
- Confirmation dialogs for easily reversible actions
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.
- 2mo ago First seen · 34 lines · 36 tokens per session scan A 381f51f139af
flow-patterns is a skill published in the GitHub repository Dragoon0x/taste-skills (7 stars, last pushed 8mo ago), licensed MIT. It adds 36 tokens to every session and 290 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
create-chatgpt-mockup
Render pixel-accurate ChatGPT mobile (iOS) screen mockups in light mode from a thread JSON. Supports user text bubbles, user image attachments, assistant markdown prose, citation chips, the OpenAI spiral logo, the Apps-SDK GPT chip in the composer, and three header styles (model-tag, plain title, "Get Plus"). Fixed…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
design-review
Five-dimension design audit (frontend UI/UX · server data-model & flow · endpoint spec · daemon-runtime/SDK & local-cache-first · built-in skill/agent-role), executed by a NON-implementing agent. Every dimension gets a verdict; N/A only with a stated reason. A dimension the design silently skipped must be surfaced as…
claude-slides
Make and revise slide decks in the Slides artifact format (project/deck.json plus one HTML file per slide) as local files, then open them in a local slide editor where the user can present, retype, drag, and export PDF, HTML or PowerPoint. Use when the user asks for an editable slide deck or presentation in this…
baoyu-design
Create or edit visual design artifacts as self-contained HTML: UI mockups, interactive prototypes, wireframes, landing pages, dashboards, app screens, slide decks, print documents, résumés, animations, 3D objects, diagrams, fliers, HTML email, and visual research reports. Also author reusable design systems, UI kits…
web-artifacts-builder
Suite of tools for creating elaborate, multi-component Prismer HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.