Borrowing it
Nothing to install: this file belongs to BostonOrange/claude-code-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BostonOrange/claude-code-framework/main/.claude/agents/performance-optimizer.mdgit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/agents/bostonorange/claude-code-framework/performance-optimizer)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/performance-optimizer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/performance-optimizer/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/agents/bostonorange/claude-code-framework/performance-optimizer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/performance-optimizer.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.00023 | $0.00546 |
| Opus 5.5 | $0.00009 | $0.00218 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 (3 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 546 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-08-31.
Other agents, from other repositories
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…