optimize-components

A command that reviews how a Next.js application divides work between Server Components and Client Components. Server Components run on the server, while Client Components are sent to the browser for interaction.

In plain words
What is it for?
Use it to find unnecessary use client directives, move data fetching to the server, split interactive pieces into smaller client components, and review component composition.
Why use it?
It helps reduce unnecessary JavaScript sent to users without removing required interactivity. It also identifies invalid data passed between the two component types.

Command for Claude Code

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/matt-dionis/claude-code-configs/optimize-components
Clone the repo
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configs

Made for: Claude Code.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 188 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.00009 $0.00188
Opus 5 $0.00005 $0.00094
Sonnet 5 $0.00002 $0.00038
Haiku 4.5 $0.00001 $0.00019

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

Security

Grade A, and why

optimize-components 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.

configurations/frameworks/nextjs-15/.claude/commands/optimize-components.md · 26 lines

What it actually says

Analyze the current component structure and optimize the Server/Client Component boundaries:

  1. Find all components currently marked with 'use client'
  2. Analyze if they truly need client-side interactivity
  3. Identify components that can be converted to Server Components
  4. Find Server Components that are passing non-serializable props
  5. Suggest component composition patterns to minimize client JS
  6. Identify opportunities for:
    • Moving data fetching to Server Components
    • Extracting interactive parts into smaller Client Components
    • Using children pattern to compose Server and Client Components

Provide a detailed report with:

  • Current client/server component ratio
  • Components that can be optimized
  • Specific refactoring suggestions
  • Estimated bundle size reduction

Focus on reducing the amount of JavaScript sent to the client while maintaining functionality.

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. 3d ago First seen · 26 lines · 9 tokens per session scan A e174ece97ecd

Subscribe to this mod's changes

optimize-components is a command published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 9 tokens to every session and 188 once invoked, about $0.0000 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-30.