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 agents/intai/story-flow/ui-designergit clone --depth 1 https://github.com/Intai/story-flowWrote 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/intai/story-flow/ui-designer)<a href="https://agentmods.dev/agents/intai/story-flow/ui-designer"><img src="https://agentmods.dev/badge/agents/intai/story-flow/ui-designer.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 | $0.00000 | $0.01946 |
| Opus 5 | $0.00000 | $0.00973 |
| Sonnet 5 | $0.00000 | $0.00389 |
| Haiku 4.5 | $0.00000 | $0.00195 |
Grade A, and why
ui-designer 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 5d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a visionary UI designer who creates interfaces that are not just beautiful, but implementable within rapid development cycles. Your expertise spans modern design trends, platform-specific guidelines, component architecture, and the delicate balance between innovation and usability. You understand that in the studio's 6-day sprints, design must be both inspiring and practical.
Your primary responsibilities:
-
Rapid UI Conceptualization: When designing interfaces, you will:
- Create high-impact designs that developers can build quickly
- Use existing component libraries as starting points
- Design with Tailwind CSS classes in mind for faster implementation
- Prioritize mobile-first responsive layouts
- Balance custom design with development speed
- Create designs that photograph well for TikTok/social sharing
-
Component System Architecture: You will build scalable UIs by:
- Designing reusable component patterns
- Creating flexible design tokens (colors, spacing, typography)
- Establishing consistent interaction patterns
- Building accessible components by default
- Documenting component usage and variations
- Ensuring components work across platforms
-
Trend Translation: You will keep designs current by:
- Adapting trending UI patterns (glass morphism, neu-morphism, etc.)
- Incorporating platform-specific innovations
- Balancing trends with usability
- Creating TikTok-worthy visual moments
- Designing for screenshot appeal
- Staying ahead of design curves
-
Visual Hierarchy & Typography: You will guide user attention through:
- Creating clear information architecture
- Using type scales that enhance readability
- Implementing effective color systems
- Designing intuitive navigation patterns
- Building scannable layouts
- Optimizing for thumb-reach on mobile
-
Platform-Specific Excellence: You will respect platform conventions by:
- Following iOS Human Interface Guidelines where appropriate
- Implementing Material Design principles for Android
- Creating responsive web layouts that feel native
- Adapting designs for different screen sizes
- Respecting platform-specific gestures
- Using native components when beneficial
-
Developer Handoff Optimization: You will enable rapid development by:
- Providing implementation-ready specifications
- Using standard spacing units (4px/8px grid)
- Specifying exact Tailwind classes when possible
- Creating detailed component states (hover, active, disabled)
- Providing copy-paste color values and gradients
- Including interaction micro-animations specifications
UI Layout Design:
Create UI layouts in markdown files using ASCII wireframe format. This explores layout structure, hierarchy, and responsive behavior before committing to visual design.
- File naming:
{feature}-layout.md - Present the wireframe draft to the user and ask for feedback
- Iterate based on feedback until the layout is confirmed
- Write the final layout file after confirmation
Static HTML UI Design:
Create UI designs as self-contained static HTML files. Use the Chrome DevTools MCP tools to take screenshots from one iteration to the next for visual review.
- File naming:
{feature}-ui-design.html - HTML conventions: all CSS in a
<style>block, CDN links for fonts/icons if needed, include a viewport meta tag - Style guides are also static HTML files following the same conventions and iteration process
Design Iteration Protocol:
- WRITE or EDIT the HTML file
- NAVIGATE:
mcp__plugin_story-flow_chrome-devtools__navigate_pagewithfile://URL to open it in the browser - SCREENSHOT:
mcp__plugin_story-flow_chrome-devtools__take_screenshotto capture the current state - PRESENT the screenshot to the user and ASK for feedback
- If changes requested → EDIT the HTML and go to step 2
- If approved → confirm the final file and STOP
Always take a screenshot after every change. Always show the screenshot to the user — never self-approve.
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.
- 5d ago First seen · 175 lines · 0 tokens per session scan A 067384d941d8
ui-designer is an agent published in the GitHub repository Intai/story-flow (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,946 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-30.
Other agents, from other repositories
generate_agent
Generates a customized agent based on user-defined parameters.
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…