ui-color

ui-color is a skill for Claude Code, Codex from Orkas-AI/Orkas. It costs 2 tokens per session (701 once invoked), scanned A, original, MIT.

A guide for choosing and reviewing interface colors, including background, text, borders, actions, status messages, charts, and dark mode.

In plain words
What is it for?
Use it to create palettes, check contrast, define light and dark themes, assign colors to interface states, and choose colors for data visualizations.
Why use it?
It helps make color choices readable, consistent, and understandable instead of reusing one color for unrelated meanings.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create palettes, check contrast, define light and dark themes, assign colors to interface states, and choose colors for data visualizations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orkas-ai/orkas/ui-color
About the project

Orkas is a desktop application for commanding a team of AI agents through one chat, with a commander model assigning work to specialist agents in parallel or in sequence. People use it to coordinate research, writing, presentations, and software tasks while keeping files on their computer. The catalogue includes skills for extending the agents available to Orkas.

Orkas-AI/Orkas · 1,885 stars · on GitHub · orkas.ai

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.

Any agent
npx skills add Orkas-AI/Orkas --skill ui-color
Clone the repo
git clone --depth 1 https://github.com/Orkas-AI/Orkas

Made for: Claude Code, Codex.

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 ui-color

README.md
[![agentmods](https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-color/github.svg)](https://agentmods.dev/skills/orkas-ai/orkas/ui-color)
Your own site
<a href="https://agentmods.dev/skills/orkas-ai/orkas/ui-color"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-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.

agentmods 80×15 button for ui-color

Your own site · 80×15
<a href="https://agentmods.dev/skills/orkas-ai/orkas/ui-color"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-color.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 701 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00002 $0.00701
Opus 5 $0.00001 $0.00351
Sonnet 5 $0.00000 $0.00140
Haiku 4.5 $0.00000 $0.00070

Measured 11d ago against content hash ae42fa56df46, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

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

resources/builtin/marketplace/agents/bcfcb4921dce/skills/ui-color/SKILL.md · 93 lines

How it starts

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

ui-color

Use this skill when creating or reviewing palettes, contrast, semantic color, dark mode, or chart colors. It adapts Color Expert-style color reasoning into practical UI work.

Color Roles First

Start with roles before choosing hues:

  • bg: page background.
  • surface: panels, rows, cards, inputs.
  • surface-raised: dialogs, menus, popovers.
  • text: primary content.
  • text-muted: metadata and helper text.
  • border: dividers, input outlines, table rules.
  • accent: primary action, selection, active state.
  • focus: visible keyboard focus.
  • danger, warning, success, info: semantic states.
  • chart-*: data series, separate from action colors.

Do not use the same accent for primary action, warning, and chart series.

OKLCH And Perceptual Rules

When authoring new palettes:

  • Prefer OKLCH/OKLAB reasoning for even lightness and chroma steps.
  • Keep neutral surfaces low-chroma.
  • Use accent chroma deliberately; high chroma should be rare in work tools.
  • Build light and dark variants by role, not by automatic inversion.
  • Keep semantic colors distinct in hue and lightness.

When the codebase uses hex, HSL, RGB, or CSS variables, implement in the local format while preserving the role logic.

Contrast Rules

Check contrast for:

  • Body text on page and panel backgrounds.
  • Muted text on surfaces.
  • Buttons in default, hover, pressed, and disabled states.
  • Inputs, focus rings, and validation messages.
  • Table row selection and hover.
  • Status chips and alerts.
  • Chart labels and legends.

Do not rely on color alone for state. Pair semantic colors with text, icon shape, position, or pattern.

Palette Construction

For product UI:

  • Use 1 primary accent.
  • Add at most 1 secondary accent unless data visualization requires more.
  • Keep neutral scale broad enough for hierarchy.
  • Keep borders visible but quiet.
  • Reserve saturated colors for action, selection, and status.

For dashboards:

  • Separate categorical chart colors from UI actions.
  • Avoid too many similar blues or purples.
  • Make critical alerts readable in both color and text.

Read the full file on GitHub · 93 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. 11d ago First seen · 93 lines · 2 tokens per session scan A ae42fa56df46

Subscribe to this mod's changes

ui-color is a skill published in the GitHub repository Orkas-AI/Orkas (1,885 stars, last pushed today), licensed MIT. It adds 2 tokens to every session and 701 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-30.