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 flitzrrr/frontend-design-skills --skill color-theorygit clone --depth 1 https://github.com/flitzrrr/frontend-design-skillsWrote 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/flitzrrr/frontend-design-skills/color-theory)<a href="https://agentmods.dev/skills/flitzrrr/frontend-design-skills/color-theory"><img src="https://agentmods.dev/badge/skills/flitzrrr/frontend-design-skills/color-theory/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/flitzrrr/frontend-design-skills/color-theory"><img src="https://agentmods.dev/badge/skills/flitzrrr/frontend-design-skills/color-theory.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.00048 | $0.01450 |
| Opus 5 | $0.00024 | $0.00725 |
| Sonnet 5 | $0.00010 | $0.00290 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
color-theory 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Color Theory
Systematic color design -- from strategic color selection to accessible dark mode.
Scope
Use this skill when: You are defining color schemes, building palettes, checking contrasts, designing dark mode, establishing semantic colors, creating design tokens for colors, or auditing existing color concepts for quality.
Principles
1. Colors Are Communication -- Not Decoration
Every color conveys a message. Color selection is a strategic decision.
2. Fewer Colors -- Stronger Impact
2-4 colors are sufficient for 95% of all projects. Primary color + accent color + neutral tones.
3. Contrast Is Mandatory
Without sufficient contrast, colors are ineffective. Contrast determines readability, hierarchy, and accessibility.
4. Consistency Across All Channels
Colors must appear identical everywhere. This requires a defined color system with named tokens.
5. Color for Function, Not Just Mood
Colors indicate status (red = error, green = success), signal interactivity, and mark relationships.
Rules
Building a Color Scheme
- DO: Minimal scheme: 1 primary color + 1 accent color + 3-5 neutral tones.
- DO: Create gradations of each color in 9-11 steps (50-950).
- DO: Define semantic colors:
success(green),warning(orange),error(red),info(blue). - DO: Use color harmonies as a starting point: complementary, analogous, or triadic.
- DON'T: Use randomly chosen colors. Each one needs justification (brand, function, emotion).
- DON'T: Use more than 5 chromatic colors (excluding neutral tones).
Color Models & Formats
- DO: Work internally with HSL (more intuitive for systematic gradations).
- DO: Use
oklch()in modern CSS for perceptually uniform gradations. - DON'T: Use CMYK on the web. CMYK is for print.
Contrast & Readability
- DO: Normal text (< 24px): at least 4.5:1 (WCAG AA).
- DO: Large text (>= 24px / >= 18.66px bold): at least 3:1 (WCAG AA).
- DO: UI components (icons, borders, focus): at least 3:1.
- DO: Simulate and test for color vision deficiency (protanopia, deuteranopia, tritanopia).
- DON'T: Use color as the ONLY differentiator. Always provide a second signal (icon, text, shape).
- DON'T: Use light pastel tones on white backgrounds for text or interactive elements.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 139 lines · 48 tokens per session scan A e835dd366538
color-theory is a skill published in the GitHub repository flitzrrr/frontend-design-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 1,450 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-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.