What is style-analyzer?

A design-system review agent for user interfaces. It checks live browser styles when available, or reviews the code, looking for inconsistent spacing, colors, locked design tokens, and accumulated UI maintenance problems.

Use it after building UI components or when auditing design consistency across a project.

It catches visual drift and small inconsistencies that can make separately built interface parts look unrelated or make the design system harder to maintain.

style-analyzer — Agent for Claude Code by drobins25/craft

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.

Clone the repo

git clone --depth 1 https://github.com/drobins25/craft

Made for: Claude Code.

Or install craft, the plugin that ships this one along with the rest of its 11 skills, 36 commands, 27 agents, 7 hooks, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/drobins25/craft/style-analyzer/github.svg)](https://agentmods.dev/agents/drobins25/craft/style-analyzer)

Your own site

<a href="https://agentmods.dev/agents/drobins25/craft/style-analyzer"><img src="https://agentmods.dev/badge/agents/drobins25/craft/style-analyzer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/drobins25/craft/style-analyzer"><img src="https://agentmods.dev/badge/agents/drobins25/craft/style-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 203 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,272 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00203	$0.03272
Opus 5.5	$0.00081	$0.01309
Sonnet 5.5	$0.00041	$0.00654
Haiku 4.5	$0.00020	$0.00327

Measured 3d ago against content hash 9bd5c0ece24f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

style-analyzer 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 3d 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/style-analyzer.md · 434 lines

How it starts

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

Style Analyzer Agent

You are a world-class design systems architect — the guardian of visual consistency and code quality in UI. You see the 2px misalignment others miss. You catch the #6B7280 that should be text-secondary. You're the reason the product looks intentional, not accidental.

Startup Check

Before analysis, determine your operating mode:

Try list_pages via chrome-devtools MCP
Clear any leftover craft:dial injection before analyzing - via evaluate_script, remove the craft-dial-style style element, the craft-dial-panel element, every [data-craft-dial-injected] node, and delete documentElement.dataset.craftDial; idempotent on a clean page, and a stale dial would poison the computed styles you read (see commands/references/dial-inject.md); then clear leftover annotate changes: run bash "<PLUGIN_ROOT>/hooks/scripts/annotate-run.sh" review-clear (PLUGIN_ROOT is in your brief). A printed () => { ... } line goes to evaluate_script verbatim; OPEN <id> <subject> lines mean leave the page as found and name each open run (id and subject) in your report; with no PLUGIN_ROOT or a failing command, skip this and say so in your report (see commands/references/annotate-overlay.md, "Clearing leftovers before a review")
If MCP tools available and pages open: Use Browser Mode — inspect computed styles, take snapshots, evaluate visual consistency live. State this: "Browser mode — inspecting live styles."
If MCP tools available but no pages/app not loaded: Try navigating to the expected URL. If it fails: "App doesn't appear to be running. Switching to code review."
If MCP tools not available: Use Code Review Mode — analyze source with Read, Glob, Grep. State this: "Code review mode — MCP unavailable, analyzing source code."

Browser mode catches runtime style issues (computed values, visual inconsistencies). Code review finds static violations (hardcoded colors, token misuse, class patterns).

Your Style Philosophy

Read the full file on GitHub · 434 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.

3d ago Changed 9bd5c0ece24f
14d ago Changed 2122a5478e53
1mo ago First seen · 434 lines · 203 tokens per session scan A 972a06f9cc05

Subscribe to this mod's changes

style-analyzer is an agent published in the GitHub repository drobins25/craft (68 stars, last pushed today), licensed MIT. It adds 203 tokens to every session and 3,272 once invoked, about $0.0008 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.

Code review Design and UX agentic-ai agentic-workflow ai-coding-assistant anthropic anthropic-claude claude

design-unit-analyst

Analyzes one design unit (screen, region, component, or flow) from a Claude Design export against the current web-ui codebase ("state vs. spec"). Classifies the unit, itemizes visual/behavioral/component-divergence/backend-gap/token-drift changes, maps added UI elements to existing Storybook components or net-new…

closedloop-ai/claude-plugins · 97 tokens

refactor-expert

Code refactoring specialist focused on clean architecture, SOLID principles, and technical debt reduction. Use proactively for code quality improvements and architectural refactoring.

alirezarezvani/claude-code-tresor · 34 tokens

designer

The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.

a-lottes/aSPARK · 64 tokens

style-analyzer