vuestrata: Skill for Claude Code

.github/skills/i-colorize/SKILL.md

i-colorize is a skill for Claude Code from boussadjra/vuestrata. It costs 26 tokens per session (1,658 once invoked), scanned A, a copy of colorize, MIT.

A design process for adding color to an interface that is mostly gray or visually flat. It first gathers the audience, use case, brand personality, and existing brand colors.

In plain words
What is it for?
Use it to identify where color can improve an interface and choose changes based on its users, purpose, and brand.
Why use it?
It prevents color choices from being made without enough context, which can lead to inconsistent or unsuitable designs.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is boussadjra/vuestrata's own configuration. It tells Claude Code how to work on vuestrata 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 vuestrata configures →

Reuse

Borrowing it

Nothing to install: this file belongs to boussadjra/vuestrata. 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/boussadjra/vuestrata/main/.github/skills/i-colorize/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/boussadjra/vuestrata

Made for: Claude Code.

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 i-colorize

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/boussadjra/vuestrata/i-colorize"><img src="https://agentmods.dev/badge/skills/boussadjra/vuestrata/i-colorize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,658 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 86% copy Near-identical to another mod 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.00026 $0.01658
Opus 5.5 $0.00010 $0.00663
Sonnet 5.5 $0.00005 $0.00332
Haiku 4.5 $0.00003 $0.00166

Measured 2mo ago against content hash b29ef63f471e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

i-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 2mo 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.

Origin

This is a copy

86% identical to colorize — 38 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/skills/i-colorize/SKILL.md · 167 lines

How it starts

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

Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality.

MANDATORY PREPARATION

Context Gathering (Do This First)

You cannot do a great job without having necessary context, such as target audience (critical), desired use-cases (critical), brand personality/tone, and especially existing brand colors.

Attempt to gather these from the current thread or codebase.

  1. If you don't find exact information and have to infer from existing design and functionality, you MUST STOP and ask the user directly to clarify what you cannot infer. whether you got it right.
  2. Otherwise, if you can't fully infer or your level of confidence is medium or lower, you MUST ask the user directly to clarify what you cannot infer. clarifying questions first to complete your context.

Do NOT proceed until you have answers. Guessing leads to generic AI slop colors.

Use frontend-design skill

Use the i-frontend-design skill for design principles and anti-patterns. Do NOT proceed until it has executed and you know all DO's and DON'Ts.


Assess Color Opportunity

Analyze the current state and identify opportunities:

  1. Understand current state:

    • Color absence: Pure grayscale? Limited neutrals? One timid accent?
    • Missed opportunities: Where could color add meaning, hierarchy, or delight?
    • Context: What's appropriate for this domain and audience?
    • Brand: Are there existing brand colors we should use?
  2. Identify where color adds value:

    • Semantic meaning: Success (green), error (red), warning (yellow/orange), info (blue)
    • Hierarchy: Drawing attention to important elements
    • Categorization: Different sections, types, or states
    • Emotional tone: Warmth, energy, trust, creativity
    • Wayfinding: Helping users navigate and understand structure
    • Delight: Moments of visual interest and personality

If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.

Read the full file on GitHub · 167 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. 2mo ago First seen · 167 lines · 26 tokens per session scan A b29ef63f471e

Subscribe to this mod's changes

i-colorize is a skill published in the GitHub repository boussadjra/vuestrata (111 stars, last pushed 11d ago), licensed MIT. It adds 26 tokens to every session and 1,658 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to colorize, differing in 38 lines, and is treated as a copy.

Related

i-colorize compared with skills from other repositories

i-colorize next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
i-colorizeboussadjra/vuestrataSkill11111d agoMITA26Claude Code
magic-uimagicuidesign/magicuiSkill23kyesterdayMITA56Claude Code, Codex
tuturuuu-satellite-app-uxtutur3u/platformSkill54todayApache-2.0A25Codex
frontend-engineerbuiphucminhtam/forgewrightSkill496d agononeA55Claude Code
frontend-designbartstc/vite-ts-react-templateSkill12313d agoMITA43Claude Code, Codex
beuistarc007/ui-componentsSkill1.9kyesterdayMITA81Claude Code, Codex
beui-prostarc007/ui-componentsSkill1.9kyesterdayMITA85Claude Code, Codex