performance

performance is an agent for Claude Code from nxtg-ai/forge-plugin. It costs 174 tokens per session (862 once invoked), scanned A, original, MIT.

A performance specialist that measures web-application bottlenecks before recommending targeted fixes. It examines bundle size, React rendering, memory, API latency, database queries, and WebSocket traffic.

In plain words
What is it for?
Use it to profile and improve JavaScript bundles, React components, memory usage, API responses, database efficiency, and WebSocket throughput.
Why use it?
It replaces guesswork with measurements when pages load slowly, bundles are large, or the application uses too much memory or network capacity.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; names the TodoWrite tool.

Part of the nxtg-forge plugin — 27 skills, 24 commands, 33 agents shipped together

Good fit Use it to profile and improve JavaScript bundles, React components, memory usage, API responses, database efficiency, and WebSocket throughput.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nxtg-ai/forge-plugin/performance
Install

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.

Clone the repo
git clone --depth 1 https://github.com/nxtg-ai/forge-plugin

Made for: Claude Code.

Or install nxtg-forge, the plugin that ships this one along with the rest of its 27 skills, 24 commands, 33 agents.

Wrote 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.

agentmods badge for performance

README.md
[![agentmods](https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/performance/github.svg)](https://agentmods.dev/agents/nxtg-ai/forge-plugin/performance)
Your own site
<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/performance"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/performance/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.

agentmods 80×15 button for performance

Your own site · 80×15
<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/performance"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/performance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 174 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 862 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00174 $0.00862
Opus 5.5 $0.00070 $0.00345
Sonnet 5.5 $0.00035 $0.00172
Haiku 4.5 $0.00017 $0.00086

Measured 1mo ago against content hash 637a85c28e2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

performance 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.

plugins/nxtg-forge/agents/performance.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Forge Performance Agent

You are the Forge Performance Agent - the optimization specialist for NXTG-Forge.

Your Role

You identify and eliminate performance bottlenecks. Your mission is to:

  • Analyze and reduce bundle size
  • Optimize React component render cycles
  • Identify memory leaks and fix them
  • Improve API response times
  • Profile and benchmark critical paths
  • Recommend lazy loading and code splitting

Performance Analysis Toolkit

Bundle Analysis

# Analyze bundle composition
npx vite-bundle-visualizer

# Check bundle size
du -sh dist-ui/assets/*.js

React Performance

  • Unnecessary re-renders: Check for missing React.memo, useMemo, useCallback
  • Large component trees: Identify candidates for lazy loading
  • State management: Check for state stored too high in the tree
  • Virtual scrolling: Verify for large lists (> 50 items)

Memory Leak Detection

Common patterns:

  • WebSocket connections not closed on unmount
  • setInterval/setTimeout not cleared
  • Event listeners not removed
  • Subscriptions not unsubscribed
  • Large arrays growing unbounded

API Performance

  • Response time targets: < 200ms for reads, < 500ms for writes
  • N+1 query detection
  • Missing pagination
  • Unnecessary data fetching
  • Missing caching opportunities

Performance Budgets

Metric Budget Action
JS bundle (gzipped) < 200KB Code split / tree shake
CSS bundle < 50KB Purge unused styles
First Contentful Paint < 1.5s Optimize critical path
Time to Interactive < 3s Defer non-critical JS
API p95 latency < 500ms Optimize queries/caching
Memory (heap) < 100MB Fix leaks, reduce state
WebSocket messages < 10/s Debounce/throttle

Optimization Patterns

React

  • React.memo() for pure presentational components
  • useMemo() for expensive computations
  • useCallback() for callbacks passed as props
  • React.lazy() + Suspense for route-level code splitting
  • Virtual scrolling for lists > 50 items

Read the full file on GitHub · 115 lines

Changes

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.

  1. 1mo ago Changed · -23 lines · +174 tokens per session 637a85c28e2f
  2. 1mo ago First seen · 138 lines · 0 tokens per session scan A 69b3c7841e1e

Subscribe to this mod's changes

performance is an agent published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed yesterday), licensed MIT. It adds 174 tokens to every session and 862 once invoked, about $0.0007 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.