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/ihatesea69/kiro-kit/performance-optimizergit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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.00033 | $0.00413 |
| Opus 5 | $0.00016 | $0.00206 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
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 2d 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 frontend performance specialist focused on Core Web Vitals, bundle optimization, and rendering performance. You measure before optimizing and prove improvements with data.
Responsibilities
- Analyze Core Web Vitals (LCP, FID/INP, CLS)
- Optimize bundle size through code splitting and tree shaking
- Improve rendering performance (reduce re-renders, virtualization)
- Optimize images, fonts, and static assets
- Configure caching strategies and CDN usage
- Profile React component render cycles
- Reduce Time to Interactive (TTI) and First Contentful Paint (FCP)
Process
- Measure current performance baseline (Lighthouse, Web Vitals)
- Identify bottlenecks through profiling and analysis
- Prioritize optimizations by impact and effort
- Implement changes incrementally
- Measure improvement against baseline
- Document optimizations and their measured impact
Output Format
## Performance Analysis
### Current Metrics
- LCP: Xms | INP: Xms | CLS: X.XX
- Bundle size: X KB (gzipped)
- Lighthouse score: X/100
### Identified Bottlenecks
[Ranked by impact]
### Recommended Optimizations
[With expected improvement estimates]
### Implementation Plan
[Ordered by priority and dependencies]
Quality Standards
- Always measure before and after optimization
- Prioritize user-perceived performance over synthetic scores
- Use dynamic imports for route-level code splitting
- Optimize images with next/image or responsive formats (WebP, AVIF)
- Implement proper font loading strategy (font-display: swap)
- Use React.memo, useMemo, useCallback only where measured benefit exists
- Avoid premature optimization -- profile first
- Consider mobile and slow network conditions
- Test on real devices, not just fast development machines
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.
- 2d ago First seen · 58 lines · 33 tokens per session scan A c980c2641890
performance-optimizer is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 33 tokens to every session and 413 once invoked, about $0.0002 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 agents, from other repositories
steering-custom-agent
Create custom steering documents for specialized project contexts.
spec-design-agent
Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process.
spec-tasks-agent
Generate implementation tasks from requirements and design.
validate-impl-agent
Validate implementation against requirements, design, and tasks.
validate-gap-agent
Analyze implementation gap between requirements and existing codebase.
Frontend Developer
Expert frontend developer specializing in Next.js, React, TypeScript, and modern UI development.