A command that helps convert CSS from one framework, preprocessor, naming method, or styling approach to another. CSS is the code that controls a website’s visual appearance.

Use it for migrations such as Sass to CSS, Bootstrap to Tailwind, legacy CSS to BEM, or CSS-in-JS to CSS Modules.

It provides a structured way to assess the existing styles, find dependencies and risky areas, and plan the conversion.

css-migrate — Command by andronics

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-migrate

Clone the repo

git clone --depth 1 https://github.com/andronics/claude-plugin-css-pro

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

When invoked 2,168 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.

Model	Per session	Once invoked
Fable 5	$0.00015	$0.02168
Opus 5	$0.00008	$0.01084
Sonnet 5	$0.00003	$0.00434
Haiku 4.5	$0.00002	$0.00217

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

Security

Grade A, and why

css-migrate 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.

commands/css-migrate.md · 438 lines

How it starts

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

CSS Migration Wizard

I'll help you migrate your CSS between different approaches, frameworks, methodologies, or preprocessors.

Arguments

/css-migrate [source-type] [target-type]

source-type: Current CSS approach target-type: Desired CSS approach

If omitted, I'll detect source and ask for target.

Supported Migrations

Preprocessor Migrations

Sass/SCSS → CSS
Less → Sass
Sass → PostCSS
Stylus → CSS

Framework Migrations

Bootstrap → Tailwind
Material UI → Custom CSS
Bulma → Custom CSS
Foundation → Modern CSS

Methodology Migrations

Legacy CSS → BEM
OOCSS → Atomic CSS
No methodology → SMACSS/ITCSS

CSS-in-JS Migrations

Styled Components → Emotion
CSS-in-JS → CSS Modules
Inline styles → CSS-in-JS
CSS-in-JS → Vanilla CSS

Migration Process

Phase 1: Analysis & Planning

I'll analyze your current setup:

Detect source type - What you're using now
Assess scope - Size and complexity
Identify dependencies - What relies on current CSS
Find risk areas - Complex components, critical pages
Estimate effort - Time and difficulty
Create migration plan - Step-by-step strategy

Phase 2: Preparation

Before migration starts:

Backup current files - Safety first
Set up coexistence - Old and new can run together
Create conversion guide - Document patterns
Set up testing - Visual regression, automated tests
Establish rollback plan - Quick revert if needed

Phase 3: Conversion

Incremental migration approach:

Start with utilities - Lowest-level styles first
Convert components - One at a time, test each
Update layouts - Page-level styles
Migrate pages - Route by route
Remove old code - Clean up after conversion

Phase 4: Validation

Ensure everything works:

Visual comparison - Before/after screenshots
Functional testing - All interactions work
Performance check - No regressions
Accessibility audit - Maintain compliance
Browser testing - Cross-browser verification

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

yesterday First seen · 438 lines · 15 tokens per session scan A 39aa73cee47b

Subscribe to this mod's changes

css-migrate is a command published in the GitHub repository andronics/claude-plugin-css-pro (2 stars, last pushed 10mo ago), licensed MIT. It adds 15 tokens to every session and 2,168 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.

Frontend

css-migrate