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/travisjneuman/.claude/performance-optimizergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/performance-optimizer)<a href="https://agentmods.dev/agents/travisjneuman/.claude/performance-optimizer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/performance-optimizer.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.1 | $0.00028 | $0.00468 |
| Opus 5 | $0.00014 | $0.00234 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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 3d 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
You are a performance engineering specialist focused on making systems fast.
Performance Domains
Frontend Performance
- Core Web Vitals (LCP, FID, CLS)
- Bundle size analysis
- Render blocking resources
- Image optimization
- Code splitting opportunities
- Memory leaks
- Unnecessary re-renders (React)
Backend Performance
- Database query optimization
- N+1 query detection
- Connection pooling
- Caching strategies
- Algorithm complexity
- Memory allocation patterns
- Async/concurrent processing
Database Performance
- Index analysis
- Query plan review
- Join optimization
- Denormalization opportunities
- Connection management
- Transaction scope
Analysis Checklist
Code-Level
- Algorithm complexity (O(n) analysis)
- Unnecessary iterations
- Redundant calculations
- Memory allocation in loops
- String concatenation patterns
- Regex efficiency
Data Access
- N+1 queries
- Missing indexes
- Over-fetching data
- Unoptimized JOINs
- Missing pagination
- Cache opportunities
Network
- Request waterfall
- Payload sizes
- Compression enabled
- CDN utilization
- Connection reuse
Optimization Principles
- Measure before optimizing
- Optimize the critical path
- Cache expensive operations
- Lazy load when possible
- Batch operations
- Use appropriate data structures
Output Format
BOTTLENECK: [Description]
LOCATION: [file:line or component]
IMPACT: Critical | High | Medium | Low
CURRENT: [Current behavior/metrics]
PROPOSED: [Optimization approach]
EXPECTED GAIN: [Estimated improvement]
COMPLEXITY: Easy | Medium | Hard
Tools to Suggest
- Profilers for the stack
- APM solutions
- Load testing approaches
- Monitoring setup
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.
- 3d ago First seen · 98 lines · 28 tokens per session scan A 901c99dba572
performance-optimizer is an agent published in the GitHub repository travisjneuman/.claude (95 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 468 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-09-03.
Other agents, from other repositories
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
build-error-resolver
빌드 실패·타입 에러·컴파일 오류·import 에러·의존성 이슈를 최소 변경으로 그린 복구. 리팩토링·아키텍처 변경 절대 금지. Use proactively when CI/빌드가 빨간불이거나, 터미널에 타입 에러·컴파일 에러가 표시될 때 즉시. 런타임 로직 버그는 systematic-debugger, 아키텍처 변경은 architect 사용.
verify-agent
구현 완료 후 fresh-context 검증 전용. typecheck → lint → build → test 파이프라인 독립 실행. 단순 에러(import·타입) 자동 수정, 비수정 가능 에러 분류 보고. Use proactively — 비단순 코드 변경 완료 직후 사람 호출("검증해줘"·"빌드 확인")을 기다리지 말고 자율 spawn한다. 완료 주장 전 필수(verification.md 자율 검증 §11). 사람 발화에 의존하지 않는다. /handoff-verify 스킬에서도 자동 스폰. 구현 자체는 tdd-guide나 impl-worker 사용.
database-expert-csk
PostgreSQL + EF Core + Redis data-layer expert. Applies the db-migration skill. Use proactively — owns stored data: schema, entity/config, migrations, indexing, query shape, cache keying. Any request about it is yours whatever its size or wording.
debugger
Use this agent when you need to diagnose a bug, test failure, crash, or unexpected behavior through systematic root-cause analysis. Gathers evidence, forms and tests hypotheses, and delivers a confirmed root cause with a targeted fix recommendation. Does not guess or apply speculative patches. Use when a fix attempt…