css-review

A review of Cascading Style Sheets (CSS), the files that control a website’s visual appearance.

In plain words
What is it for?
Checking CSS organization, repeated rules, color contrast, keyboard focus, readable text, animations, responsive layouts, and compatibility.
Why use it?
It helps find styling problems that affect code upkeep, accessibility for people with disabilities, loading speed, or browser support.

Command

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/andronics/claude-plugin-css-pro/css-review
Clone the repo
git clone --depth 1 https://github.com/andronics/claude-plugin-css-pro
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 816 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.00014 $0.00816
Opus 5 $0.00007 $0.00408
Sonnet 5 $0.00003 $0.00163
Haiku 4.5 $0.00001 $0.00082

Measured 2d ago against content hash 5d94378e9180, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

css-review 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 2d 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.

commands/css-review.md · 157 lines

How it starts

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

CSS Code Review

I'll perform a comprehensive review of your CSS, checking for best practices, accessibility, performance, and maintainability issues.

Review Scope

Analyzing: $ARGUMENTS

If no specific files provided, I'll review all CSS files in the project.

What I'll Check

1. Code Quality & Organization

  • File structure and organization
  • Naming conventions consistency
  • Methodology adherence (BEM, OOCSS, etc.)
  • Code duplication
  • Selector specificity
  • Code comments and documentation

2. Accessibility (WCAG 2.2)

  • Color contrast ratios
  • Focus indicators
  • Text sizing and readability
  • Screen reader compatibility
  • Motion and animation accessibility
  • Keyboard navigation support

3. Performance

  • Bundle size analysis
  • Selector efficiency
  • Render-blocking issues
  • Animation performance
  • Unused CSS detection
  • Critical CSS opportunities

4. Browser Compatibility

  • Modern CSS feature usage
  • Missing vendor prefixes
  • Fallback strategies
  • Feature query usage

5. Best Practices

  • CSS architecture patterns
  • Responsive design implementation
  • Maintainability concerns
  • Anti-patterns and code smells

Review Process

  1. Scan all CSS files - Identify files and analyze structure
  2. Run static analysis - Check with Stylelint (if configured)
  3. Calculate metrics - Specificity, complexity, bundle size
  4. Check accessibility - Contrast ratios, focus styles
  5. Performance audit - Expensive selectors, render triggers
  6. Generate report - Prioritized findings with recommendations

Report Format

I'll provide a detailed report with:

Summary

  • Overall assessment
  • Total issues found
  • Critical issues count
  • Quick wins

Issues by Priority

🔴 CRITICAL - Must fix (security, accessibility blockers)

  • Issue description
  • Location (file:line)
  • Why it's critical
  • How to fix

🟠 IMPORTANT - Should fix (performance, best practices)

  • Issue description
  • Impact analysis
  • Recommended solution

Read the full file on GitHub · 157 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. 2d ago First seen · 157 lines · 14 tokens per session scan A 5d94378e9180

Subscribe to this mod's changes

css-review is a command published in the GitHub repository andronics/claude-plugin-css-pro (2 stars, last pushed 10mo ago), licensed MIT. It adds 14 tokens to every session and 816 once invoked, about $0.0001 per session on Opus 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-31.