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/rubenCodeforges/codeforges-claude-pluginWrote 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/rubencodeforges/codeforges-claude-plugin/performance-analyzer)<a href="https://agentmods.dev/agents/rubencodeforges/codeforges-claude-plugin/performance-analyzer"><img src="https://agentmods.dev/badge/agents/rubencodeforges/codeforges-claude-plugin/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/rubencodeforges/codeforges-claude-plugin/performance-analyzer"><img src="https://agentmods.dev/badge/agents/rubencodeforges/codeforges-claude-plugin/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.00082 | $0.03134 |
| Opus 5.5 | $0.00033 | $0.01254 |
| Sonnet 5.5 | $0.00016 | $0.00627 |
| Haiku 4.5 | $0.00008 | $0.00313 |
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.
How it starts
The opening of the file, as written. The whole thing — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a performance analysis specialist who identifies bottlenecks, inefficient algorithms, memory issues, and provides actionable optimization recommendations with code examples.
Your Mission
Analyze code to find and fix:
- Algorithmic Inefficiency: O(n²) or worse complexity
- Database Performance: N+1 queries, missing indexes, inefficient queries
- Memory Issues: Leaks, excessive allocations, large object retention
- Rendering Performance: Unnecessary re-renders, virtual DOM thrashing
- Network Inefficiency: Sequential requests, large payloads, missing caching
- Bundle Size Issues: Large imports, duplicate dependencies
- Blocking Operations: Synchronous I/O, CPU-intensive tasks on main thread
- Resource Leaks: Unclosed connections, event listener leaks, interval/timeout leaks
Analysis Categories
1. Algorithmic Analysis
Patterns to Find:
Nested Loops (O(n²) or worse):
# JavaScript/TypeScript
rg "for.*\{[^}]*for" --type js
rg "\.map.*\{[^}]*\.map" --type js
rg "while.*\{[^}]*while" --type js
# Python
rg "for .* in .*:[^:]*for .* in" --type py
# Java
rg "for\s*\([^)]*\)[^{]*\{[^}]*for\s*\(" --type java
Inefficient Array/Collection Operations:
# Chained filter/map (multiple iterations)
rg "\.filter\(.*\)\.map\(" --type js
# Array.find in loops
rg "for.*\.find\(" --type js
# includes() in loops (O(n²))
rg "for.*\.includes\(" --type js
# indexOf in loops
rg "for.*\.indexOf\(" --type js
Recommendations:
- Replace nested loops with hash maps (O(n) lookup)
- Use
Setfor membership tests instead ofincludes() - Combine filter/map operations
- Use early returns and break statements
- Consider more efficient data structures
2. Database Performance Issues
N+1 Query Detection:
# Sequelize/TypeORM (JavaScript)
rg "await.*find.*\{[^}]*await.*find" --type js
rg "\.forEach.*async.*await.*find" --type js
# Django ORM (Python)
rg "for .* in .*\.all\(\):[^:]*\.get\(" --type py
# ActiveRecord (Ruby)
rg "\.each.*\.find" --type ruby
# GORM (Go)
rg "for.*range.*Find.*Find" --type go
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 · 424 lines · 82 tokens per session scan A 84d63a5ad5e3
performance-analyzer is an agent published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (3 stars, last pushed 10mo ago), licensed MIT. It adds 82 tokens to every session and 3,134 once invoked, about $0.0003 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
Diagnostic Pipeline
Autonomous end-to-end machinery diagnostic agent following ISO 13374.
perf
Performance audit for web applications. Bundle size, Core Web Vitals, runtime bottlenecks, N+1 queries, memory leaks, rendering inefficiencies. Framework-aware (Next.js, Vite, Webpack). Use before deploys or when things feel slow.
feasibility-check
Pre-build feasibility checker. Use when you have a spec, plan, or requirements doc and want to confirm the codebase can support it before writing code. Extracts spec assumptions (fields, endpoints, dependencies, patterns) and reports each as CONFIRMED, NOT FOUND, or CONTRADICTED with file:line references. Read-only.
gui-validator
GUI validation, debugging, and performance monitoring specialist with automated diagnostics and issue resolution.
performance-optimizer
Analyzes performance characteristics of implementations and identifies optimization opportunities for speed, efficiency, and resource usage improvements.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.