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/rubencodeforges/codeforges-claude-plugin/performance-analyzergit clone --depth 1 https://github.com/rubenCodeforges/codeforges-claude-pluginWhat 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.00082 | $0.03134 |
| Opus 5 | $0.00041 | $0.01567 |
| Sonnet 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 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.
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.
- 2d 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 (2 stars, last pushed 9mo ago), licensed MIT. It adds 82 tokens to every session and 3,134 once invoked, about $0.0004 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
Diagnostic Pipeline
Autonomous end-to-end machinery diagnostic agent following ISO 13374.
Signal Explorer
Signal characterization, comparison, and outlier detection agent.
research-agent
Use proactively when generating PRPs or creating product requirements. Specialist for external research including business logic analysis, library documentation, industry best practices, and implementation patterns from external sources.
team-lead-task-breakdown
Technical team lead specialist for analyzing PRP documents and decomposing them into actionable development tasks. Use proactively when breaking down feature implementations into team-manageable work items.
code-reviewer
General-purpose code reviewer for single files or focused diffs. Use when reviewing specific files or a single diff before merging. Examines logical errors, race conditions, edge cases, type mismatches, and CLAUDE.md compliance. Reports issues by severity with file:line references. For multi-file PR or pre-merge…
wp
Principal WordPress developer following Human Made and 10up engineering standards. Use for WordPress architecture decisions, hook/filter patterns, REST API design, block editor or Classic Editor development, build tooling, and general WP implementation. For read-only WP code review, use wp-reviewer instead. Adapts to…