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.
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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.
[](https://agentmods.dev/commands/matt-dionis/claude-code-configs/optimize-bundle)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/optimize-bundle"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/optimize-bundle/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.
<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/optimize-bundle"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/optimize-bundle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00005 | $0.01128 |
| Opus 5.5 | $0.00002 | $0.00451 |
| Sonnet 5.5 | $0.00001 | $0.00226 |
| Haiku 4.5 | $0.00001 | $0.00113 |
Grade A, and why
optimize-bundle 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.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze bundle size and optimize for production.
Instructions
- Run bundle analysis
- Identify large dependencies
- Find unused code
- Implement optimization strategies
- Generate optimization report
Analysis Tools
Next.js
# Install bundle analyzer
npm install -D @next/bundle-analyzer
# Configure next.config.js
const withBundleAnalyzer = require('@next/bundle-analyzer')({
enabled: process.env.ANALYZE === 'true',
})
module.exports = withBundleAnalyzer({
// your config
})
# Run analysis
ANALYZE=true npm run build
Vite
# Install rollup plugin
npm install -D rollup-plugin-visualizer
# Add to vite.config.ts
import { visualizer } from 'rollup-plugin-visualizer'
plugins: [
visualizer({
open: true,
gzipSize: true,
brotliSize: true,
})
]
# Run build
npm run build
General
# webpack-bundle-analyzer
npm install -D webpack-bundle-analyzer
# source-map-explorer
npm install -D source-map-explorer
npm run build
npx source-map-explorer 'build/static/js/*.js'
Optimization Strategies
1. Code Splitting
// Dynamic imports
const HeavyComponent = lazy(() => import('./HeavyComponent'))
// Route-based splitting (Next.js)
export default function Page() {
return <div>Auto code-split by route</div>
}
// Conditional loading
if (userNeedsFeature) {
const module = await import('./feature')
module.initialize()
}
2. Tree Shaking
// ❌ Bad - imports entire library
import _ from 'lodash'
// ✅ Good - imports only what's needed
import debounce from 'lodash/debounce'
// For shadcn/ui - already optimized!
// Components are copied, not imported from package
3. Component Optimization
// Memoize expensive components
const MemoizedComponent = memo(ExpensiveComponent)
// Lazy load heavy components
const Chart = lazy(() => import('./Chart'))
<Suspense fallback={<Skeleton />}>
<Chart />
</Suspense>
4. Asset Optimization
// Next.js Image optimization
import Image from 'next/image'
<Image
src="/hero.jpg"
width={1200}
height={600}
priority
alt="Hero"
/>
// Font optimization
import { Inter } from 'next/font/google'
const inter = Inter({
subsets: ['latin'],
display: 'swap',
})
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.
- 1mo ago First seen · 220 lines · 5 tokens per session scan A 00ebf37450f8
optimize-bundle is a command published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 1,128 once invoked, about $0.0000 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.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.