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 mtarcure/claude-vibe-squad --skill color-theorygit clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/mtarcure/claude-vibe-squad/color-theory)<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.
<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>- NVIDIA SkillSpector warn
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.
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.00062 | $0.00301 |
| Opus 5.5 | $0.00025 | $0.00120 |
| Sonnet 5.5 | $0.00012 | $0.00060 |
| Haiku 4.5 | $0.00006 | $0.00030 |
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 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.
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
- State the job the palette must do: hierarchy, mood, brand fit, and any accessibility target.
- 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.
- Check contrast for every text/background pair against the WCAG target (hand off measurement to
wcag-conformance-audit); never ship a pair on vibes. - Account for color meaning/culture and color-vision deficiency; ensure no state is encoded by hue alone.
- 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.
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.
- 2mo ago First seen · 22 lines · 62 tokens per session scan A d0c26128940d
color-theory is a skill published in the GitHub repository mtarcure/claude-vibe-squad (211 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 301 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
ui-mockup
Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing.
taste-profile
Build a scoped taste profile packet from examples, preferences, and explicit dislikes so downstream agents can make style decisions without inventing the user's taste.
diagram-drawio
Use when the user requests diagrams, flowcharts, architecture diagrams, ER diagrams, UML / sequence / class diagrams, network topology, ML/DL model figures (Transformer/CNN/LSTM), mind maps, or any visualization. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that…
software-design-lifecycle-solution-design-biz-arch-diagramming
A method for designing and reviewing a business-solution architecture: a middle-level view that connects confirmed business problems to a solution before technical implementation is designed.
software-design-lifecycle-tech-overview-system-arch-diagramming
A guide for architects who draw or review system architecture diagrams during overview design. It explains subsystems, outside dependencies, communication links, and system boundaries without going into every technology detail.