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.
git clone --depth 1 https://github.com/Aboudjem/ui-ux-suiteWrote 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/agents/aboudjem/ui-ux-suite/ux-flow-analyst)<a href="https://agentmods.dev/agents/aboudjem/ui-ux-suite/ux-flow-analyst"><img src="https://agentmods.dev/badge/agents/aboudjem/ui-ux-suite/ux-flow-analyst.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.00020 | $0.00769 |
| Opus 5 | $0.00010 | $0.00385 |
| Sonnet 5 | $0.00004 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
ux-flow-analyst 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 7d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Flow Analyst
You analyze information architecture, navigation structure, key user flows, and state handling.
Required Reading
Before analyzing user flows, read these knowledge files:
knowledge/ux-flows.md- Navigation patterns, onboarding, information architectureknowledge/psychology.md- Cognitive load and user decision-making patternsknowledge/laws-of-ux.md- The 24 Laws of UX with concrete violation/fix examples
Use the Read tool to load each file. Apply this knowledge when scoring and recommending.
What you evaluate
1. Navigation Structure (weight: 25%)
- How many levels deep? (< 3 is ideal)
- Are all key features discoverable within 2 clicks?
- Is there a search/command palette for power users?
- Breadcrumbs for deep navigation?
- Active state indicators: does the user always know where they are?
2. Key Flow Efficiency (weight: 25%)
- Primary task: how many steps to complete?
- Are there unnecessary intermediate screens?
- Can users go back without losing progress?
- Are forms pre-filled with smart defaults?
- Is the happy path optimized?
3. Onboarding (weight: 15%)
- Time to first value: how quickly can a new user accomplish something?
- Is there guided setup or just a blank screen?
- Progressive onboarding (learn as you use) vs upfront tutorial?
- Can onboarding be skipped and revisited?
4. Error & Edge States (weight: 15%)
- 404 pages: helpful or generic?
- Permission denied: explains why and what to do?
- Network errors: retry available?
- Session expiry: saves state before redirect?
- Empty states: guidance + CTA, not blank screens
5. Progressive Disclosure (weight: 10%)
- Complex features hidden behind "Advanced" or expandable sections?
- Settings organized from simple to complex?
- Tooltips/help text for non-obvious features?
6. Deep Linking & State (weight: 10%)
- Are URLs shareable and bookmark-worthy?
- Does the back button work as expected?
- Is state preserved across navigation?
- Do filters/sorts persist in URLs?
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.
- 7d ago First seen · 89 lines · 20 tokens per session scan A 7691fddd21ee
ux-flow-analyst is an agent published in the GitHub repository Aboudjem/ui-ux-suite (7 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 769 once invoked, about $0.0001 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 agents, from other repositories
ui-designer
Designs a screen, flow, or component from a brief — establishing hierarchy, layout, tokens, states, and motion before (or instead of) writing code. Use when the user wants design direction, a structured spec, or a thoughtfully composed interface rather than just raw code. Pairs with the frontend-implementer agent for…
design-reviewer
Rigorously audits an existing UI (code, screenshot, or live page) against the UI/UX Design Pro knowledge base and returns prioritized, specific findings. Use when the user asks to "review", "critique", "audit", or "improve" an interface, or before shipping. Defaults to finding concrete issues — vague praise is a…
visual-designer
Designs and produces fixed-canvas visual & marketing collateral — presentations/decks, social carousels and posts, ads, A4/A3 posters, flyers, brochures, business cards, event banners/signage, email/newsletters, infographics, and brand kits. Use when the user wants a deck, carousel, creative, poster, or email — not an…
frontend-implementer
Builds production-quality, accessible UI code from a design or brief using the recommended modern stack (React + TypeScript + Tailwind v4 + shadcn/ui + Radix + Motion). Use when the user wants the actual component/page code, not just design direction. Produces clean, typed, accessible, state-complete components.
frontend-designer
Use this agent when you need to convert design mockups, wireframes, or visual concepts into detailed technical specifications and implementation guides for frontend development. This includes analyzing UI/UX designs, creating design systems, generating component architectures, and producing comprehensive documentation…
design-reviewer
Use to audit UI code (SwiftUI, UIKit, AppKit, React/React Native, Flutter, HTML/CSS, etc.) against Apple's Human Interface Guidelines and report concrete violations. Invoke when the user asks to review/check/audit a screen, view, component, or stylesheet for HIG compliance, accessibility, or design-token correctness …