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/matt-dionis/claude-code-configs/analyze-performancegit 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/analyze-performance)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/analyze-performance"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/analyze-performance.svg" alt="Measured on agentmods" 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 | $0.00007 | $0.00285 |
| Opus 5 | $0.00003 | $0.00143 |
| Sonnet 5 | $0.00001 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
analyze-performance 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 5d 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.
What it actually says
Perform a comprehensive performance analysis of the Next.js application:
Bundle Analysis
- Check if @next/bundle-analyzer is installed, install if needed
- Run build with ANALYZE=true to generate bundle analysis
- Identify large dependencies and opportunities for code splitting
Core Web Vitals Analysis
- Check for Web Vitals monitoring setup
- Analyze current implementation for:
- Largest Contentful Paint (LCP) issues
- Cumulative Layout Shift (CLS) problems
- First Input Delay (FID) / Interaction to Next Paint (INP)
Code Analysis
- Find components not using dynamic imports where appropriate
- Check image optimization (using next/image properly)
- Verify font optimization (using next/font)
- Analyze third-party script loading strategies
- Check for unnecessary client-side data fetching
Caching Analysis
- Review fetch caching strategies
- Check for proper use of revalidate
- Analyze static vs dynamic rendering choices
Generate Report
Create a detailed performance report with:
- Current bundle size metrics
- Largest dependencies
- Optimization opportunities ranked by impact
- Specific code changes needed
- Estimated performance improvements
Save the report to performance-report.md with actionable recommendations.
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.
- 5d ago First seen · 47 lines · 7 tokens per session scan A 5fab2488b568
analyze-performance is a command published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 285 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.