design-check

design-check is a command for Claude Code from isaacsight/kernel. It costs 0 tokens per session (375 once invoked), scanned A, original, MIT.

A design-audit command that checks recent changes against the Rubin design system and common accessibility requirements.

In plain words
What is it for?
Use it to review changed CSS and interface files for typography, color, button size, dark mode, semantic HTML, and accessibility issues.
Why use it?
It catches inconsistent fonts, colors, touch targets, dark-mode styles, labels, focus indicators, and contrast problems before they reach users.

Command for Claude Code

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.

agentmods
npx agentmods add commands/isaacsight/kernel/design-check
Clone the repo
git clone --depth 1 https://github.com/isaacsight/kernel

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 design-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/isaacsight/kernel/design-check.svg)](https://agentmods.dev/commands/isaacsight/kernel/design-check)
Your own site
<a href="https://agentmods.dev/commands/isaacsight/kernel/design-check"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/design-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 375 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00375
Opus 5 $0.00000 $0.00187
Sonnet 5 $0.00000 $0.00075
Haiku 4.5 $0.00000 $0.00038

Measured yesterday against content hash 03c93feadb72, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design-check 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 yesterday.

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.

.claude/commands/design-check.md · 30 lines

What it actually says

Run a design audit against the Rubin design system.

You are the Designer Agent. Read .claude/agents/designer.md for your full protocol and Rubin specs.

Steps:

  1. Load memory — Call agent_memory_read for designer agent
  2. Check diff — Run git diff --stat to identify changed files (focus on .css, .tsx, .ts files)
  3. Design lint — Run kernel_design_lint on any changed files
  4. Typography audit — Verify all text uses EB Garamond (prose) or Courier Prime (mono). Flag any system fonts, sans-serif, or unknown font families.
  5. Color palette audit — Verify colors match Rubin tokens: ivory (#FAF9F6), slate (#1F1E1D), vignette blue. Flag any hardcoded hex values not in the palette.
  6. Touch target audit — Verify all buttons and interactive elements meet 44x44px minimum (36x36 for inline actions, 40x40 for header icons).
  7. Dark mode audit — Check that every light-mode style has a [data-theme="dark"] counterpart.
  8. Accessibility audit — Check for ARIA labels on icon buttons, semantic HTML, focus indicators, color contrast.
  9. Save findings — Call agent_memory_write for designer with findings
  10. Handoff — If issues affect functionality (not just style), call team_handoff to qa

Report format:

# Design Audit — [date]

## Summary
[X] critical | [X] warnings | [X] notes

## Findings
[Severity | Location | Issue | Fix for each]

## Verdict: PASS / FAIL
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. yesterday First seen · 30 lines · 0 tokens per session scan A 03c93feadb72

Subscribe to this mod's changes

design-check is a command published in the GitHub repository isaacsight/kernel (16 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 375 tokens. 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-09-03.