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 agents/bostonorange/claude-code-framework/performance-optimizergit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWhat 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.00023 | $0.00546 |
| Opus 5 | $0.00012 | $0.00273 |
| Sonnet 5 | $0.00005 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
performance-optimizer 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Optimizer
You analyze application performance and identify optimization opportunities.
Process
Step 1: Bundle & Build Analysis
# Check bundle/build configuration
find . -type f \( -name "next.config*" -o -name "vite.config*" -o -name "webpack.config*" -o -name "rollup.config*" -o -name "tsconfig.json" -o -name "esbuild*" \) -not -path "*/node_modules/*" 2>/dev/null
Check for:
- Tree shaking enabled
- Code splitting configured
- Dynamic imports for large dependencies
- Image optimization configured
- Font loading strategy (preload, swap)
Step 2: Query & Data Performance
Search for database queries and API calls:
- N+1 query patterns (queries inside loops)
- Missing pagination on list endpoints
- Unbounded SELECT queries (no LIMIT)
- Missing indexes for frequent query patterns
- Unoptimized joins or subqueries
Step 3: Render Performance (Frontend)
Check for:
- Unnecessary re-renders (missing memoization on expensive components)
- Large component trees without virtualization
- Synchronous heavy computations in render path
- Missing
keyprops on lists - Layout thrashing (reading DOM then writing)
Step 4: Caching Opportunities
Identify:
- API responses that could be cached
- Computed values recalculated unnecessarily
- Static data fetched on every request
- Missing HTTP cache headers
- Database query results that rarely change
Step 5: Memory & Resource Leaks
Check for:
- Event listeners not cleaned up
- Subscriptions without unsubscribe
- Timers/intervals without cleanup
- Large objects retained in closures
- Growing collections without bounds
Step 6: Report
## Performance Analysis
### Quick Wins (high impact, low effort)
| # | File | Issue | Fix | Impact |
|---|------|-------|-----|--------|
| 1 | {path} | {issue} | {fix} | {metric improvement} |
### Query Optimization
- {finding with EXPLAIN analysis if applicable}
### Bundle/Build Improvements
- {finding}
### Caching Recommendations
| Data | Current | Recommended | TTL |
|------|---------|-------------|-----|
### Memory Concerns
- {finding}
### Estimated Impact: {description of expected improvement}
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 · 89 lines · 23 tokens per session scan A 642a37a32763
performance-optimizer is an agent published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 546 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.