colorize

colorize is a command for Claude Code from Muminur/frontend-design-craft-skill. It costs 6 tokens per session (674 once invoked), scanned A, original, MIT.

A command for creating or revising a website colour system using OKLCH, a colour format designed to make perceived lightness and colour differences easier to control. It publishes the colours as CSS custom properties and checks text contrast.

In plain words
What is it for?
Use it to define brand, neutral, status, hover, and active colours for a website and verify WCAG AA contrast.
Why use it?
It replaces ad-hoc colour choices with a consistent palette and helps ensure text remains readable against its background.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the craft plugin — 4 skills, 13 commands shipped together

Good fit Use it to define brand, neutral, status, hover, and active colours for a website and verify WCAG AA contrast.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/muminur/frontend-design-craft-skill/colorize
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Muminur/frontend-design-craft-skill

Made for: Claude Code.

Or install craft, the plugin that ships this one along with the rest of its 4 skills, 13 commands.

Wrote 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.

agentmods badge for colorize

README.md
[![agentmods](https://agentmods.dev/badge/commands/muminur/frontend-design-craft-skill/colorize.svg)](https://agentmods.dev/commands/muminur/frontend-design-craft-skill/colorize)
Your own site
<a href="https://agentmods.dev/commands/muminur/frontend-design-craft-skill/colorize"><img src="https://agentmods.dev/badge/commands/muminur/frontend-design-craft-skill/colorize.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 674 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00006 $0.00674
Opus 5 $0.00003 $0.00337
Sonnet 5 $0.00001 $0.00135
Haiku 4.5 $0.00001 $0.00067

Measured 7d ago against content hash 10269bbe7dfd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

colorize 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 7d 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.

commands/colorize.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/colorize

Build or fix a color system. Author in OKLCH; ship as CSS custom properties.

Target

$ARGUMENTS

Procedure

  1. Identify the brand color. If unclear, ask the user. Avoid defaulting to blue.
  2. Build the palette. A complete palette for most sites is 4–6 colors:
    • Tinted neutral scale — 8–10 stops, all sharing the brand hue at very low chroma (oklch(98% 0.005 H) to oklch(15% 0.02 H) where H is the brand hue).
    • Brand color — used sparingly for primary action, one or two accents.
    • Semantic set — success, warning, error, info. Each at 2–3 lightness stops.
  3. Check perceptual uniformity. OKLCH lets you generate hover/active states by stepping lightness, not by adding black or white. --brand-hover: oklch(from var(--brand) calc(l - 4%) c h).
  4. Verify contrast. Every text-on-background combination must hit WCAG AA (4.5:1 for body, 3:1 for large). Tools: browser devtools, contrast-checker CLIs.
  5. Apply restraint. The palette has 12 tokens; the page should still feel like it uses 3–4. The rest are for states, not primaries.

Banned color moves

  • Pure #000 text or #FFF backgrounds in content
  • Purple → blue, pink → orange, teal → blue gradients
  • Using Tailwind default colors (blue-500, etc.) directly in components without a semantic alias
  • Gradient text
  • More than one gradient moment per page

Output

/* Example output structure */
:root {
  /* Brand */
  --brand: oklch(60% 0.18 250);
  --brand-hover: oklch(56% 0.18 250);
  --brand-active: oklch(52% 0.18 250);

  /* Tinted neutrals (8 stops) */
  --neutral-0: oklch(99% 0.003 250);
  --neutral-50: oklch(96% 0.005 250);
  --neutral-100: oklch(92% 0.007 250);
  /* ... */
  --neutral-900: oklch(18% 0.015 250);

  /* Semantic */
  --success: oklch(60% 0.15 145);
  --warning: oklch(70% 0.15 75);
  --error:   oklch(58% 0.20 25);
  --info:    oklch(60% 0.15 230);
}

Show the user the palette as a visual swatch (HTML or markdown table) before applying changes.

Read the full file on GitHub · 59 lines

Changes

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.

  1. 7d ago First seen · 59 lines · 6 tokens per session scan A 10269bbe7dfd

Subscribe to this mod's changes

colorize is a command published in the GitHub repository Muminur/frontend-design-craft-skill (4 stars, last pushed 3mo ago), licensed MIT. It adds 6 tokens to every session and 674 once invoked, about $0.0000 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.