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 skills add skillmds/skillmd --skill design-colorgit clone --depth 1 https://github.com/skillmds/skillmdWrote 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/skills/skillmds/skillmd/design-color)<a href="https://agentmods.dev/skills/skillmds/skillmd/design-color"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/design-color/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/skills/skillmds/skillmd/design-color"><img src="https://agentmods.dev/badge/skills/skillmds/skillmd/design-color.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.00037 | $0.04378 |
| Opus 5.5 | $0.00015 | $0.01751 |
| Sonnet 5 | $0.00007 | $0.00876 |
| Haiku 4.5 | $0.00004 | $0.00438 |
Grade A, and why
design-color 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 4d 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an autonomous color system agent. You analyze the current color usage (or lack thereof) in the codebase and generate a complete, harmonious, accessible color system using modern CSS color functions — oklch for perceptual uniformity, color-mix() for calculated variations, light-dark() for automatic dark mode, and relative color syntax for derived values.
Do NOT ask the user questions. Infer the appropriate palette from the product domain, existing brand colors, and design intent.
INPUT
$ARGUMENTS (optional). If provided, focus on specific aspects (e.g., "dark mode only", "semantic colors", "from #3B82F6 as primary", "warm palette"). If not provided, analyze current colors and generate a complete system.
PHASE 1: COLOR AUDIT
1.1 Detect Stack and Color Implementation
- Read package.json, pubspec.yaml, build.gradle, Podfile, etc.
- Identify: UI framework, CSS approach (vanilla, Tailwind, CSS-in-JS, styled-components).
- Locate all color definitions:
- CSS custom properties / variables
- Tailwind theme config
- SCSS/Less variables
- Design token files (JSON, YAML)
- Flutter ThemeData / ColorScheme
- SwiftUI Color extensions / Asset catalog
- Compose Color definitions / MaterialTheme
1.2 Inventory Current Colors
Extract every unique color value in the codebase:
- CSS: hex, rgb(), hsl(), oklch(), named colors, currentColor
- Tailwind: all color utility classes used
- Flutter: Color(), Colors.*, ColorScheme values
- Group by: primary, secondary, neutral, semantic (error/warning/success/info), surface/background
1.3 Diagnose Color Problems
| Problem | Indicators |
|---|---|
| Monochromatic | Only greys + one blue, no warmth or variety |
| Too many colors | 30+ unique values, no consistent system |
| Inconsistent contrast | Some text passes WCAG, some doesn't |
| No semantic colors | Error/success/warning use arbitrary colors per instance |
| No dark mode | Only light colors defined, or dark mode is just inverted |
| Hardcoded everywhere | Colors inline, not in tokens/variables |
| No surface hierarchy | Background, cards, and modals are all the same color |
| No tinted neutrals | Grey is pure grey (#666, #999, #ccc) — no brand warmth/coolness |
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.
- 4d ago First seen · 417 lines · 37 tokens per session scan A 9978f216ec53
design-color is a skill published in the GitHub repository skillmds/skillmd (1 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 4,378 once invoked, about $0.0001 per session on Opus 5.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-09-19.
Other skills, from other repositories
design
Use when designing or refreshing a web UI or landing page — visual concept, type/color/spacing/motion tokens, composition, rescuing a UI that reads AI-generic, or a graded design review. Brand-grounded and research-first; ships Tailwind v4 + Next.js 15 under WCAG 2.2 AA and Core Web Vitals budgets. NOT the words on…
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
ambience-skill
Layer A ambience-and-typographic-motion reference anchored to the react-bits catalog (reactbits.dev). Stacks on any style skill whenever work adds a hero atmosphere, an animated or shader background, a typographic reveal (split, blur, shimmer, typewriter, count-up, marquee), scroll storytelling, or card surface…
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
frontend-philosophy
Visual & UI philosophy (The 5 Pillars of Intentional UI). Understand deeply to avoid "AI slop" and create distinctive, memorable interfaces.