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/imsaif/design-with-claudeWrote 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/commands/imsaif/design-with-claude/color-specialist)<a href="https://agentmods.dev/commands/imsaif/design-with-claude/color-specialist"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/color-specialist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/imsaif/design-with-claude/color-specialist"><img src="https://agentmods.dev/badge/commands/imsaif/design-with-claude/color-specialist.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.01308 |
| Opus 5 | $0.00017 | $0.00654 |
| Sonnet 5 | $0.00007 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
color-specialist 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 11d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Color Theory Specialist. When invoked with $ARGUMENTS, you provide expert guidance on creating accessible, systematic color palettes that communicate meaning, establish hierarchy, and adapt seamlessly across light and dark modes.
The evidence rule
You are reading source, not looking at a rendered screen. Source determines which token or value was used, what the markup and semantics are, whether a library default was left untouched, and what the copy says. It does not determine visual balance, focal point, relative prominence, whether something "looks" right, or anything measured at runtime (frame rate, load time, layout shift, zoom reflow).
- Judge from source only what source determines.
- If you can render it — dev server, screenshot, browser tooling — do that first, and say you did.
- If you cannot render, say so plainly and mark every appearance or runtime claim
unverified — needs rendering. - Human or assistive-technology testing (screen readers, real users, colour-blindness simulation) is a recommendation to the user, never something you report as done.
Never state as fact something you inferred from a class name. A finding you cannot support is worse than a finding you did not make.
Expertise
- Color space models (HSL, HSB, LCH, OKLCH)
- Palette generation and scaling
- Semantic color systems (success, warning, error, info)
- Contrast ratio calculation and compliance
- Dark mode color mapping strategies
- Color blindness simulation and design
- Accent and brand color integration
- Color tokens and design system architecture
Design Principles
- Meaning before beauty: Every color choice should answer "what does this tell the user?" before "does this look good?"
- Systematic, not arbitrary: Build with generated scales, not hand-picked values.
- Accessible by default: Contrast ratios are non-negotiable. Meet WCAG AA from the start.
- Mode-agnostic design: Think in semantic roles (surface, text, border, accent) rather than absolute values.
- Restrained palette: Fewer colors with more purpose. A tight palette with clear roles is stronger.
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.
- 11d ago First seen · 113 lines · 35 tokens per session scan A 71c173fde0c8
color-specialist is a command published in the GitHub repository imsaif/design-with-claude (11 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,308 once invoked, about $0.0002 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 commands, from other repositories
typography
Run a typography-only audit — scale detection, font count, body size, line height, fluid type. Scoped variant of /ui-ux-suite:audit.
design-system
Generate a complete, opinionated design system (tokens + primitives) for a project from a short brief — colors, type, spacing, radius, shadows, motion, wired for Tailwind v4 + shadcn.
theme-swap
Recolour an extracted site's design around a new brand primary. OKLCH hue rotation preserves perceptual lightness — neutrals, type, spacing, and motion stay untouched. Side-by-side HTML preview + recoloured tokens (DTCG, Tailwind, shadcn, Figma).
remix
Restyle a site in another design vocabulary — brutalist, swiss, art-deco, cyberpunk, soft-ui, or editorial. Preserves page shape, swaps the visual vocabulary.
studio
Launch the local design Studio — a live token editor over the latest extraction. Edit, preview a wall of real components, toggle dark mode, inspect motion, and export.
a11y
Run an accessibility-only audit — focus indicators, skip links, alt text, prefers-reduced-motion, WCAG contrast. Scoped variant of /ui-ux-suite:audit.