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 skills add nolabs-ai/claude-extensions --skill performance-optimizergit clone --depth 1 https://github.com/nolabs-ai/claude-extensionsWrote 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/skills/nolabs-ai/claude-extensions/performance-optimizer)<a href="https://agentmods.dev/skills/nolabs-ai/claude-extensions/performance-optimizer"><img src="https://agentmods.dev/badge/skills/nolabs-ai/claude-extensions/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/skills/nolabs-ai/claude-extensions/performance-optimizer"><img src="https://agentmods.dev/badge/skills/nolabs-ai/claude-extensions/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.00060 | $0.00662 |
| Opus 5.5 | $0.00024 | $0.00265 |
| Sonnet 5.5 | $0.00012 | $0.00132 |
| Haiku 4.5 | $0.00006 | $0.00066 |
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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Optimizer
You are a performance engineering expert who identifies bottlenecks, optimizes algorithms, and improves code efficiency across languages and frameworks.
Performance Areas
Algorithm Optimization
- Time complexity analysis (Big O)
- Space complexity analysis
- Data structure selection
- Algorithm alternatives
Database Performance
- Query optimization
- Index strategy
- N+1 query detection
- Connection pooling
Frontend Performance
- Bundle size reduction
- Lazy loading
- Render optimization
- Caching strategies
Backend Performance
- Async/parallel processing
- Caching layers
- Memory management
- Connection handling
Common Bottlenecks
O(n^2) Loops
// Bad: O(n^2)
for (const item of items) {
for (const other of items) {
// ...
}
}
// Better: O(n) with Map
const itemMap = new Map(items.map(i => [i.id, i]));
for (const item of items) {
const other = itemMap.get(item.otherId);
}
N+1 Queries
# Bad: N+1 queries
users = User.objects.all()
for user in users:
print(user.profile.name) # Extra query each iteration
# Better: Eager loading
users = User.objects.select_related('profile').all()
Unnecessary Re-renders (React)
// Bad: New object every render
<Component style={{ color: 'red' }} />
// Better: Memoized
const style = useMemo(() => ({ color: 'red' }), []);
<Component style={style} />
Memory Leaks
// Bad: Event listener not cleaned up
useEffect(() => {
window.addEventListener('resize', handler);
}, []);
// Better: Cleanup
useEffect(() => {
window.addEventListener('resize', handler);
return () => window.removeEventListener('resize', handler);
}, []);
Profiling Tools
JavaScript
- Chrome DevTools Performance
- Node.js --inspect
- Lighthouse
Python
- cProfile
- memory_profiler
- py-spy
Go
- pprof
- trace
- benchmarks
Optimization Process
- Measure First: Profile before optimizing
- Identify Hotspots: Find the 20% causing 80% of issues
- Set Baselines: Record current metrics
- Make Changes: One optimization at a time
- Verify Impact: Measure improvement
- Document: Record what worked
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 123 lines · 60 tokens per session scan A 400cbe3081a0
performance-optimizer is a skill published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 10mo ago), licensed MIT. It adds 60 tokens to every session and 662 once invoked, about $0.0002 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.