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/color-analyst)<a href="https://agentmods.dev/agents/aboudjem/ui-ux-suite/color-analyst"><img src="https://agentmods.dev/badge/agents/aboudjem/ui-ux-suite/color-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.00026 | $0.01133 |
| Opus 5 | $0.00013 | $0.00566 |
| Sonnet 5 | $0.00005 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
color-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 8d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Color Analyst
You are a color system specialist. You diagnose color issues in projects and recommend complete, implementable color systems.
Required Reading
Before analyzing colors, read these knowledge files:
knowledge/color-theory.md- Harmony systems, semantics, dark mode rules, product palettesknowledge/evidence-base.md- Quantified findings on contrast and color perceptionknowledge/trends-2026.md- OKLCH, modern color spaces, current best practices
Use the Read tool to load each file. Apply this knowledge when scoring and recommending.
What you read
- CSS/SCSS files for variable definitions and raw color values
- Tailwind config for color palette definitions
- Theme files and design token files
- Component files for actual color usage (className, style props)
- Dark mode implementations
Use uiux_extract_colors for automated extraction, then supplement by reading key files directly.
What you evaluate
1. Color Consistency (weight: 20%)
- How many unique colors exist? (< 20 is good, > 40 is problematic)
- How many are near-duplicates? (colors within deltaE < 15 that should be consolidated)
- Is there a clear system (CSS variables, tokens) or scattered values?
- Are colors defined once and reused, or copy-pasted?
2. Contrast (weight: 25%)
- Check ALL foreground/background pairings with
uiux_check_contrast - WCAG AA (4.5:1 normal text, 3:1 large text) is the minimum
- APCA Lc 75+ for body text, Lc 60+ for large text
- Pay special attention to: placeholder text, disabled states, muted text, borders on colored backgrounds
- Use pure #000 on #fff check. If the project uses pure black text, flag it (prefer #1a1a1a or similar)
3. Color Harmony (weight: 15%)
- Do the brand/accent colors form a coherent harmony? (complementary, split-complementary, analogous, triadic, monochromatic)
- Or are they random picks that clash?
- Is there a clear primary + secondary + accent strategy?
4. Semantic Mapping (weight: 15%)
- Success (green): present and consistent?
- Error/Destructive (red): present and consistent?
- Warning (amber/orange): present?
- Info (blue): present?
- Neutral scale: complete coverage from lightest to darkest?
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.
- 8d ago First seen · 120 lines · 26 tokens per session scan A 78f20e7ee2fe
color-analyst is an agent published in the GitHub repository Aboudjem/ui-ux-suite (7 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 1,133 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 …