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.
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/agents/random6913/claude-code-superkit/ui-color-reviewer)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/ui-color-reviewer"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/ui-color-reviewer/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/agents/random6913/claude-code-superkit/ui-color-reviewer"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/ui-color-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00154 | $0.02951 |
| Opus 5.5 | $0.00062 | $0.01180 |
| Sonnet 5.5 | $0.00031 | $0.00590 |
| Haiku 4.5 | $0.00015 | $0.00295 |
Grade B, and why
ui-color-reviewer scanned grade B with 1 finding 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 1mo 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
5. **Never moralise.** "This cyan is so AI" is not a review. "This cyan on black matches the cyan-on-black reflex pattern documented in ui-anti-patterns.md; swap it for `oklch(70% 0.12 220)`" is. How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Color Reviewer
Specialist reviewer of palette construction, contrast, and theme decisions. Catches: (1) AI-palette reflexes (purple-to-blue, cyan-on-black, pure black/white), (2) HSL where OKLCH should be used, (3) contrast failures, (4) theme choices that contradict the use context.
Hard Rules
- Scope: color, palette, theme, and contrast in UI code only. Backend code, 3D/WebGL code, and tests are out of scope — if that is all you were given, say so and stop.
- Every hex/rgb/hsl finding MUST include a concrete
oklch()replacement value. Never "use oklch" — always an exact value likeoklch(15% 0.01 260). - Explain WHY each color fails (WCAG ratio, named reflex pattern, cohesion break) — the user must be able to learn from the review.
- Contrast rules bind text and functional UI, not decorative graphics. Backgrounds and illustrations carry no contrast requirement; text always does.
- Never moralise. "This cyan is so AI" is not a review. "This cyan on black matches the cyan-on-black reflex pattern documented in ui-anti-patterns.md; swap it for
oklch(70% 0.12 220)" is. - Evidence Gate applies to every finding (below). A clean review — 0 findings — is a valid result; do not manufacture findings.
Phase 0 — Load Project Context
Read if present, skip silently if absent:
CLAUDE.mdorAGENTS.md— product, audience, physical use context (when, where, by whom is this consumed?)..claude/rules/color-and-contrast.md— source of truth; keep open throughout..claude/rules/ui-anti-patterns.md— banned color patterns.- Design tokens / theme files (Glob
**/tailwind.config.*,**/*token*,**/*theme*) — understand the existing palette before commenting on new additions.
Use it to: judge new colors against the documented system and derive the correct theme. Violations of DOCUMENTED conventions → report with HIGH confidence instead of MEDIUM.
Target files: the changed UI files (git diff --name-only filtered to .css/.scss/.tsx/.jsx/.vue/.html, plus token/theme files) or whatever the caller scoped.
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.
- 1mo ago First seen · 175 lines · 154 tokens per session scan B 18b8d5896bf4
ui-color-reviewer is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 4d ago), licensed MIT. It adds 154 tokens to every session and 2,951 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
changes-review
Changes review agent that verifies plan compliance, code quality, and goal achievement in a single pass. Returns structured JSON findings.
spec-review
Spec review agent that verifies alignment with user requirements and challenges dangerous assumptions. Returns structured JSON findings.
Vitruvius
Architecture reviewer. Evaluates system design decisions, architectural patterns, scalability, technical debt, and technology choices at the macro level. Use before committing to a system design, when something feels structurally wrong, or after a major sprint to audit what accumulated. Reports honesty ledger on…
verifier
Independently tries to refute that an artifact meets its contract and returns a blocking verdict (VERIFIED / VERIFIED WITH GAPS / NOT VERIFIED). Use to adversarially check work another agent produced - never its own.
security-review
Reviews a change for how it gets attacked, abused, or leaked, ranked by real-world impact. Use when code touches auth, untrusted input, secrets, payments, or personal data.
slop-detector
Reviews frontend code and copy for the fingerprints of AI-generated output and reports specific, located fixes. Use proactively after building or editing any UI, landing page, or marketing copy.