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.
git clone --depth 1 https://github.com/ypollak2/claude-code-kickstartWrote 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/ypollak2/claude-code-kickstart/performance-analyzer)<a href="https://agentmods.dev/agents/ypollak2/claude-code-kickstart/performance-analyzer"><img src="https://agentmods.dev/badge/agents/ypollak2/claude-code-kickstart/performance-analyzer/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/ypollak2/claude-code-kickstart/performance-analyzer"><img src="https://agentmods.dev/badge/agents/ypollak2/claude-code-kickstart/performance-analyzer.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.00024 | $0.00517 |
| Opus 5.5 | $0.00010 | $0.00207 |
| Sonnet 5.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 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.
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.
- 1mo 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 6mo ago), licensed MIT. It adds 24 tokens to every session and 517 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
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could…
type-design-analyzer
Use this agent when you need expert analysis of type design in your codebase. Specifically use it (1) when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, (2) during pull request creation to review all types being added, and (3) when refactoring existing types to…
issue-tracer2
Takes any GitHub Issue, traces root cause through the codebase, and drives it to full resolution (fix + tests + PR).
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.
jd-fix-agent
Judgment Day surgical fix agent for confirmed findings. Can edit code and run focused tests.
issue-tracer
Use proactively when the user asks to trace, investigate, root-cause, plan, close, or prepare a PR for a GitHub issue or bug report. Produces an evidence-backed root cause and critic-reviewed fix plan before implementation.