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.
npx agentmods add commands/andronics/claude-plugin-css-pro/css-initgit clone --depth 1 https://github.com/andronics/claude-plugin-css-proWhat 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.00011 | $0.00958 |
| Opus 5 | $0.00005 | $0.00479 |
| Sonnet 5 | $0.00002 | $0.00192 |
| Haiku 4.5 | $0.00001 | $0.00096 |
Grade A, and why
css-init 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CSS Project Initialization
I'll help you set up a new CSS project with an appropriate architecture and best practices.
Analyzing Project Context
First, let me analyze your project to understand what you're building:
- Checking for existing files and frameworks
- Detecting project type (React, Vue, vanilla, etc.)
- Identifying build tools (Webpack, Vite, etc.)
- Understanding project scale and requirements
Architecture Options
Based on your project, I can set up:
1. Vanilla CSS with BEM
Best for: Static sites, small projects, traditional web apps
Structure:
css/
├── base/
│ ├── reset.css
│ ├── typography.css
│ └── variables.css
├── components/
│ ├── button.css
│ ├── card.css
│ └── form.css
├── layouts/
│ ├── header.css
│ ├── footer.css
│ └── grid.css
├── utilities/
│ └── helpers.css
└── main.css
2. Sass/SCSS with ITCSS
Best for: Medium to large projects, traditional architecture
Structure:
scss/
├── settings/
│ └── _variables.scss
├── tools/
│ └── _mixins.scss
├── generic/
│ └── _reset.scss
├── elements/
│ └── _typography.scss
├── objects/
│ └── _layouts.scss
├── components/
│ ├── _button.scss
│ └── _card.scss
├── utilities/
│ └── _helpers.scss
└── main.scss
3. CSS Modules
Best for: React, Vue, or component-based frameworks
Structure:
src/
├── components/
│ ├── Button/
│ │ ├── Button.tsx
│ │ └── Button.module.css
│ └── Card/
│ ├── Card.tsx
│ └── Card.module.css
├── styles/
│ ├── globals.css
│ └── variables.css
└── App.tsx
4. Utility-First (Tailwind-like)
Best for: Rapid development, design systems
Setup:
- Configure Tailwind CSS or create custom utility system
- Set up PostCSS with plugins
- Configure PurgeCSS for production
5. CSS-in-JS
Best for: React apps, dynamic styling needs
Options:
- Styled Components
- Emotion
- Vanilla Extract (zero-runtime)
- Linaria (zero-runtime)
What I'll Set Up
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 · 163 lines · 11 tokens per session scan A 4c143c26f445
css-init is a command published in the GitHub repository andronics/claude-plugin-css-pro (2 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 958 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.