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 MrBlushu/blushu-design-skills --skill make-it-flowgit clone --depth 1 https://github.com/MrBlushu/blushu-design-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/mrblushu/blushu-design-skills/make-it-flow)<a href="https://agentmods.dev/skills/mrblushu/blushu-design-skills/make-it-flow"><img src="https://agentmods.dev/badge/skills/mrblushu/blushu-design-skills/make-it-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.
<a href="https://agentmods.dev/skills/mrblushu/blushu-design-skills/make-it-flow"><img src="https://agentmods.dev/badge/skills/mrblushu/blushu-design-skills/make-it-flow.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.00116 | $0.01890 |
| Opus 5 | $0.00058 | $0.00945 |
| Sonnet 5 | $0.00023 | $0.00378 |
| Haiku 4.5 | $0.00012 | $0.00189 |
Grade A, and why
make-it-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 10d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make It Flow
Turn a concrete interface problem into a coherent, testable interaction model. Implement only when the user explicitly requests a build or change; keep review and advice read-only.
Workflow
-
Set scope and mode.
- Classify the request as design, revision, implementation, or review.
- Limit mixed requests to the interaction-pattern portion and name any necessary handoff.
- Route away unresolved product discovery, pure visual direction, generic usability review, text editing, certification, and unrelated debugging.
- If the primary request is a generic audit or asks for everything wrong without naming an interaction-pattern decision, stop after stating that boundary and the appropriate handoff. Do not manufacture a pattern decision from the artifact or produce audit findings.
-
Inspect before proposing.
- Read supplied artifacts and search the workspace for the existing implementation before asking for more context.
- Require a concrete artifact for implementation or review: repository files, a screenshot, prototype, flow, recording, or sufficiently detailed markup/specification.
- Locate established components, routes, state ownership, data loading, empty/error states, and relevant tests.
- Distinguish observed facts, supported inferences, assumptions, and unknowns.
-
Capture the decision context.
- Record the task, actors, frequency, content scale, platform, input methods, state lifetime, latency, risk, and constraints only when they can change the choice.
- Treat missing evidence as an assumption. Ask only when alternatives would produce materially different, costly, or irreversible work; otherwise choose a reversible default and flag it.
-
Model the interaction before controls.
- List the relevant objects, actions, states, relationships, transitions, entry, exit, failure, and recovery.
- Identify the dominant screen purpose and navigation topology when applicable.
- Remove unnecessary steps or unclear state boundaries before selecting a pattern.
What ships with it
7 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.
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.
- 10d ago First seen · 134 lines · 116 tokens per session scan A da0f3447dd2f
make-it-flow is a skill published in the GitHub repository MrBlushu/blushu-design-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 116 tokens to every session and 1,890 once invoked, about $0.0006 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.
Other skills, from other repositories
anti-ui-slop
Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.
image-director
The Creative Design Manager — manages ALL visual design production under 1ai-content. Delegates to logo design, icon design, banner design, UI/UX, and brand design system. Has memory via 1ai-hub brain, follows 1ai-rules, and provides visual assets to Content Director, Marketing Director, and Sales Director. Use when…
tsq-ui
A method for planning screens and user journeys before building them. It uses simple wireframes—rough screen layouts—and flow diagrams showing how users move through an interface.
carrier-product-review
A product-review guide for telecommunications products such as mobile apps, service plans, billing systems, and customer or business platforms.
frontend-design
Design and implement context-fit frontend interfaces with deliberate art direction, accessible interaction, responsive behavior, complete states, and rendered verification. Use when creating or substantially reworking pages, components, product workspaces, dashboards, marketing sites, editorial surfaces, commerce…
claude-design
Design one-off HTML artifacts (landing, deck, prototype).