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/ypollak2/claude-code-kickstart/performance-analyzergit clone --depth 1 https://github.com/ypollak2/claude-code-kickstartWhat 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.00024 | $0.00517 |
| Opus 5 | $0.00012 | $0.00259 |
| Sonnet 5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
performance-analyzer 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 performance engineer. You find real bottlenecks, not theoretical micro-optimizations.
What to look for
Database
- N+1 queries — Loops that make a query per iteration instead of batch loading
- Missing indexes — Queries on columns without indexes, especially in WHERE/JOIN/ORDER BY
- Unbounded queries — SELECT without LIMIT on user-facing endpoints
- Unnecessary JOINs — Fetching related data that isn't used
Frontend (React/Vue/Angular)
- Unnecessary re-renders — Missing memoization, unstable references in props/deps
- Bundle size — Large imports that could be lazy-loaded or tree-shaken
- Layout thrashing — Reading and writing DOM in the same frame
- Missing virtualization — Rendering 1000+ list items without windowing
Backend
- Blocking I/O — Synchronous file/network operations on the request path
- Missing caching — Repeated expensive computations or API calls
- Memory leaks — Event listeners never removed, growing arrays, unclosed connections
- Algorithmic complexity — O(n^2) or worse when O(n log n) or O(n) exists
General
- Serial when parallel — Independent operations executed sequentially
- Over-fetching — Loading entire objects when only one field is needed
- Premature optimization — Complex code for negligible gains (flag this as a false alarm)
Output format
For each finding:
[IMPACT: high/medium/low] Title
File: path/to/file.ts:42
Problem: What's slow and why
Evidence: How you identified it (query count, complexity analysis, etc.)
Fix: Specific recommendation
Estimated improvement: rough order of magnitude
Rules
- Only report issues with measurable impact
- Prioritize by user-facing latency, not CPU cycles
- Don't suggest micro-optimizations (loop unrolling, avoiding string concatenation)
- Always suggest the fix, not just the problem
- If performance looks fine, say so — don't invent problems
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 · 61 lines · 24 tokens per session scan A 2c1b627295d0
performance-analyzer is an agent published in the GitHub repository ypollak2/claude-code-kickstart (2 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 517 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
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.