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 skills/genkovich/sdd/ux-flowsnpx skills add genkovich/sdd --skill ux-flowsgit clone --depth 1 https://github.com/genkovich/sddWrote 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/genkovich/sdd/ux-flows)<a href="https://agentmods.dev/skills/genkovich/sdd/ux-flows"><img src="https://agentmods.dev/badge/skills/genkovich/sdd/ux-flows.svg" alt="Measured on agentmods" 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.00216 | $0.02107 |
| Opus 5 | $0.00108 | $0.01053 |
| Sonnet 5 | $0.00043 | $0.00421 |
| Haiku 4.5 | $0.00022 | $0.00211 |
Grade A, and why
ux-flows 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 6d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: ux-flows
Draws how the user moves through a UI-touching feature — after clarify, before design. For
each UI-touching §4 user story it produces a mermaid flowchart (happy path + the alt/error
branches the §5 ACs demand), builds the screen inventory (SCR-NN — the id contract screens
details later), and maps every UI-touching AC to the flow/branch that shows it. The artifact is
always markdown + mermaid whatever docs/design-system.md picks as the drawing tool — flows
are flow-altitude, not visual design. design then reads it as evidence for the
target-surface + UI-architecture decisions (the formal target_surfaces declaration stays
design's); sequences aligns UI-driven flows on the SCR ids; plan-tests takes the
e2e-through-UI paths from here.
This stage is optional by surface, not by size: its N/A condition (no human-facing UI) lives in
../_shared/size-matrix.md and is evaluated by clarify's handoff
(specify's when clarify was legally skipped). Invoked directly, it always runs.
Question phrasing → ../_shared/ask-style.md; each diagram is confirmed
in prose, never as raw mermaid → ../_shared/diagram-presentation.md.
Flow labels + prose follow artifact_language — mermaid keywords, SCR ids and AC ids stay English
→ ../_shared/artifact-language.md.
Owner
PM + designer (or whoever owns the user experience). The PM confirms each flow matches a real user
story; the Tech Lead flags flows that imply architecture (they become design input, not decisions
here).
Inputs
<slug>— feature slug.- Gate (hard-refuse if missing):
docs/features/<slug>/spec.md— the flows derive from §4 user stories + §5 ACs. Absent → STOP: «runspecify <slug>first — ux-flows derives from its user stories». - (Expected)
docs/design-system.md— the platform posture (the default platform assumption) + the tool. Absent → not a block: work incode-mode assumptions, recommend/sdd:design-systemin the handoff. - (Optional)
CONTEXT.md(both levels, per-feature wins) — canonical roles for the actors. - (Optional)
docs/features/<slug>/.size/.route— depth + handoff resolution; absent → default M / standard and say so in the handoff.
What ships with it
1 file 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.
- 6d ago First seen · 125 lines · 216 tokens per session scan A 2156781965ff
ux-flows is a skill published in the GitHub repository genkovich/sdd (119 stars, last pushed yesterday), licensed MIT. It adds 216 tokens to every session and 2,107 once invoked, about $0.0011 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…