react-performance

A set of techniques for making React interfaces faster by reducing unnecessary component updates, shrinking downloaded code, and avoiding delayed chains of data requests.

In plain words
What is it for?
Use it to optimize React components, prevent unnecessary re-renders, split or lazy-load code, improve initial loading, and investigate performance issues.
Why use it?
It helps diagnose slow rendering, large initial downloads, and request waterfalls, where each request waits for the previous one.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/macromania/agentop/react-performance
Any agent
npx skills add macromania/agentop --skill react-performance
Clone the repo
git clone --depth 1 https://github.com/macromania/agentop

Made for: Claude Code, Codex.

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,010 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00061 $0.03010
Opus 5 $0.00030 $0.01505
Sonnet 5 $0.00012 $0.00602
Haiku 4.5 $0.00006 $0.00301

Measured yesterday against content hash 1fba80b06a36, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

react-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 yesterday.

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.

.github/skills/react-performance/SKILL.md · 475 lines

How it starts

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

React Performance Optimization

Performance patterns to prevent unnecessary re-renders, reduce bundle size, and create responsive UIs.

When to Use This Skill

  • Optimizing slow components
  • Reducing bundle size
  • Fixing unnecessary re-renders
  • Improving initial load time
  • Debugging performance issues

Critical: Prevent Waterfalls

Impact: CRITICAL - The highest impact optimization.

What is a Waterfall?

Sequential requests where each waits for the previous:

Timeline:
[----Parent Data Fetch----]
                           [----Child Data Fetch----]
                                                     [----Grandchild Fetch----]
Total: 900ms

Anti-Pattern: Fetch on Mount

// ❌ BAD: Creates waterfall
function ParentComponent() {
  const [data, setData] = useState(null);
  
  useEffect(() => {
    fetchParentData().then(setData);  // Child waits for this
  }, []);
  
  if (!data) return <Loading />;
  return <ChildComponent parentId={data.id} />;
}

function ChildComponent({ parentId }: { parentId: string }) {
  const [childData, setChildData] = useState(null);
  
  useEffect(() => {
    fetchChildData(parentId).then(setChildData);  // Waits for parent
  }, [parentId]);
  
  return <div>{childData?.name}</div>;
}

Solution: Parallel Data Fetching

// ✅ GOOD: Fetch in parallel at top level
function ParentComponent() {
  const { parentData, childData, isLoading } = useParallelData();
  
  if (isLoading) return <Loading />;
  
  return (
    <div>
      <ParentView data={parentData} />
      <ChildView data={childData} />
    </div>
  );
}

function useParallelData() {
  const [data, setData] = useState({ parentData: null, childData: null });
  const [isLoading, setIsLoading] = useState(true);
  
  useEffect(() => {
    Promise.all([fetchParentData(), fetchChildData()])
      .then(([parentData, childData]) => {
        setData({ parentData, childData });
        setIsLoading(false);
      });
  }, []);
  
  return { ...data, isLoading };
}

Read the full file on GitHub · 475 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. yesterday First seen · 475 lines · 61 tokens per session scan A 1fba80b06a36

Subscribe to this mod's changes

react-performance is a skill published in the GitHub repository macromania/agentop (10 stars, last pushed 5mo ago), licensed MIT. It adds 61 tokens to every session and 3,010 once invoked, about $0.0003 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.