claude-vibe-squad: Skill for Claude Code

.agents/skills/color-theory/SKILL.md

color-theory is a skill for Claude Code, Codex from mtarcure/claude-vibe-squad. It costs 62 tokens per session (301 once invoked), scanned A, original, MIT.

A guide for creating a reusable color palette for a visual system. It assigns colors to roles such as backgrounds, text, and interaction states while considering cultural meaning and color-vision deficiency.

In plain words
What is it for?
Use it to choose a color harmony, define light and dark color tokens, assign semantic roles, and plan accessible interaction states.
Why use it?
It helps keep colors consistent and usable across an interface. It also prevents interactions from being communicated by hue alone, which some people cannot distinguish.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is mtarcure/claude-vibe-squad's own configuration. It tells Claude Code and Codex how to work on claude-vibe-squad itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-vibe-squad configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mtarcure/claude-vibe-squad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mtarcure/claude-vibe-squad/main/.agents/skills/color-theory/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mtarcure/claude-vibe-squad

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

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

agentmods 80×15 button for color-theory

Your own site · 80×15
<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/color-theory"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/color-theory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 301 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high YARA Match · line 4
    YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
    Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.00062 $0.00301
Opus 5 $0.00031 $0.00151
Sonnet 5 $0.00012 $0.00060
Haiku 4.5 $0.00006 $0.00030

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

Security

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.

.agents/skills/color-theory/SKILL.md · 22 lines

What it actually says

Color Theory

Choose and justify a color system for a design by mechanism — harmony, contrast, and meaning — not by taste alone.

Steps

  1. State the job the palette must do: hierarchy, mood, brand fit, and any accessibility target.
  2. Build the palette from a defined relationship (complementary, analogous, triadic, mono) plus neutrals; give each role a name (primary/accent/surface/text), not just a hex.
  3. Check contrast for every text/background pair against the WCAG target (hand off measurement to wcag-conformance-audit); never ship a pair on vibes.
  4. Account for color meaning/culture and color-vision deficiency; ensure no state is encoded by hue alone.
  5. Define the palette as tokens with light/dark values so the system, not a one-off, carries the color.

Acceptance

  • Each color has a named role and a stated relationship to the others.
  • Every text/background pair meets the declared contrast target; no hue-only signaling.
  • The palette is expressed as reusable tokens, not scattered hex values.
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 · 22 lines · 62 tokens per session scan A d0c26128940d

Subscribe to this mod's changes

color-theory is a skill published in the GitHub repository mtarcure/claude-vibe-squad (148 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 301 once invoked, about $0.0003 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.

Related

Other skills, from other repositories