optimize-config

optimize-config is a command for Claude Code from Matt-Dionis/claude-code-configs. It costs 21 tokens per session (2,629 once invoked), scanned A, original, MIT.

A command for reviewing and tuning a Tailwind CSS setup, including which files it scans and how its generated styles are built.

In plain words
What is it for?
Use it to inspect CSS bundle size, adjust content paths, clean up Tailwind configuration, and tune development or production builds.
Why use it?
It helps reduce unused CSS and can improve build performance by removing unnecessary configuration, plugins, and theme settings.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is npx tailwindcss -i ./src/styles.css -o ./dist/output.css.

Good fit Use it to inspect CSS bundle size, adjust content paths, clean up Tailwind configuration, and tune development or production builds.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configs
agentmods
npx agentmods add commands/matt-dionis/claude-code-configs/optimize-config

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 optimize-config

README.md
[![agentmods](https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/optimize-config/github.svg)](https://agentmods.dev/commands/matt-dionis/claude-code-configs/optimize-config)
Your own site
<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/optimize-config"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/optimize-config/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.

agentmods 80×15 button for optimize-config

Your own site · 80×15
<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/optimize-config"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/optimize-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 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,629 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.02629
Opus 5.5 $0.00008 $0.01052
Sonnet 5.5 $0.00004 $0.00526
Haiku 4.5 $0.00002 $0.00263

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

Security

Grade A, and why

optimize-config 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 1mo 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.

configurations/ui/tailwindcss/.claude/commands/optimize-config.md · 413 lines

How it starts

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

Optimize TailwindCSS Configuration

This command analyzes and optimizes your TailwindCSS setup for maximum performance and minimal bundle size.

What This Command Does

  1. Content Path Optimization

    • Analyzes project structure to optimize content scanning
    • Configures precise file patterns for better purging
    • Excludes unnecessary directories and files
  2. Bundle Size Analysis

    • Identifies unused utilities in your CSS bundle
    • Optimizes safelist configuration
    • Configures effective CSS purging strategies
  3. Build Performance

    • Optimizes PostCSS pipeline configuration
    • Configures caching strategies
    • Sets up development vs production optimizations
  4. Plugin and Theme Cleanup

    • Removes unused plugins and theme extensions
    • Optimizes custom utility configurations
    • Cleans up redundant theme settings

Usage Examples

Analyze Current Bundle Size

# Build CSS and analyze size
npx tailwindcss -i ./src/styles.css -o ./dist/output.css
wc -c ./dist/output.css

# With minification
npx tailwindcss -i ./src/styles.css -o ./dist/output.css --minify
wc -c ./dist/output.css

# Compress with Brotli
brotli -q 11 ./dist/output.css
ls -lh ./dist/output.css.br

Content Path Optimization

// Before: Generic paths
module.exports = {
  content: ["./src/**/*.{js,jsx,ts,tsx}"],
}

// After: Specific optimized paths
module.exports = {
  content: [
    // Be specific about directories
    './pages/**/*.{js,ts,jsx,tsx,mdx}',
    './components/**/*.{js,ts,jsx,tsx}',
    './app/**/*.{js,ts,jsx,tsx}',
    './lib/**/*.{js,ts}',
    
    // Include component libraries if used
    './node_modules/@your-ui-lib/**/*.{js,ts,jsx,tsx}',
    
    // Exclude unnecessary files
    '!./node_modules',
    '!./.git',
    '!./.next',
    '!./dist',
    '!./coverage',
  ],
}

Advanced Content Configuration

module.exports = {
  content: [
    {
      files: ['./src/**/*.{js,ts,jsx,tsx}'],
      // Custom extraction for complex patterns
      transform: {
        js: (content) => {
          // Extract classes from template literals
          return content.match(/(?:class|className)(?:Name)?[`:=]\s*[`"']([^`"']*)[`"']/g) || []
        }
      }
    },
    {
      files: ['./components/**/*.{js,ts,jsx,tsx}'],
      // Extract dynamic class compositions
      transform: {
        jsx: (content) => {
          const matches = content.match(/(?:clsx|cn|twMerge)\([^)]*\)/g) || []
          return matches.join(' ')
        }
      }
    }
  ]
}

Read the full file on GitHub · 413 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. 1mo ago First seen · 413 lines · 21 tokens per session scan A 3f26acc027c7

Subscribe to this mod's changes

optimize-config is a command published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 21 tokens to every session and 2,629 once invoked, about $0.0001 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-09-03.