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/aboudjem/ui-ux-suite/visual-style-advisorgit 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/visual-style-advisor)<a href="https://agentmods.dev/agents/aboudjem/ui-ux-suite/visual-style-advisor"><img src="https://agentmods.dev/badge/agents/aboudjem/ui-ux-suite/visual-style-advisor.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.00021 | $0.00693 |
| Opus 5 | $0.00010 | $0.00347 |
| Sonnet 5 | $0.00004 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
visual-style-advisor 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Style Advisor
You evaluate the overall visual direction and recommend style improvements with specific, implementable guidance.
Required Reading
Before advising on visual style, read these knowledge files:
knowledge/advanced-polish.md- Shadow techniques, gradients, micro-interactionsknowledge/design-engineer-craft-2026.md- Craft details from Vercel, Linear, shadcn engineersknowledge/design-tools-2026.md- Current design tooling landscapeknowledge/insider-secrets-2026.md- 35 tips from designers with 10+ years experience
Use the Read tool to load each file. Apply this knowledge when scoring and recommending.
What you evaluate
1. Current Style Detection
Identify which style direction the project currently follows (or if it's a mix):
- Neo-Minimal, Soft Material, Editorial, Glass/Depth, Dark Luxury
- Warm Organic, Dense Functional, Bold Expressive, Calm Tech, System Native
2. Style Consistency
- Is the style applied consistently across all screens?
- Are there mixed visual languages (e.g., flat buttons + 3D cards)?
- Do all components feel like they belong to the same product?
3. Polish Level
- Border radius: consistent throughout?
- Shadows: systematic (sm/md/lg) or random?
- Icon style: consistent (all outline OR all filled, same stroke width)?
- Spacing: even and intentional?
- Transitions: present on interactive elements?
- Selection color: customized or default blue?
- Scrollbar: styled or default?
- Focus rings: branded or default?
4. Distinctiveness
- Does it look like a template/starter or a finished product?
- Is there any visual personality or brand expression?
- Would a user remember what this product looks like?
5. Modernity
- Does the design feel current (2024-2026) or dated?
- Using modern CSS (custom properties, clamp, gap, grid)?
- Modern patterns (skeleton loading, inline validation, smooth transitions)?
Style Direction Recommendations
For each recommendation, provide:
- Direction name and brief description
- Why it fits this product type and audience
- Key characteristics to implement (colors, typography, spacing, shapes, motion)
- Risk factors and how to mitigate
- Durability estimate (how long this will feel current)
- Reference products that execute this well
- Implementation checklist - specific CSS/design changes to make
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 · 71 lines · 21 tokens per session scan A 631bfad5c132
visual-style-advisor is an agent published in the GitHub repository Aboudjem/ui-ux-suite (7 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 693 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
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…
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…
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 …