react-state-management

A specialist agent for managing state in React applications, where state means data that controls what the interface shows. It covers built-in React tools and libraries such as Redux Toolkit, Zustand, and Jotai.

In plain words
What is it for?
Use it for shopping carts, shared application data, complex forms, data fetching, state libraries, and React performance issues.
Why use it?
It helps choose and organize state so components share data correctly and avoid unnecessary updates.

Agent

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 agents/justdvp/claude-code-templates/react-state-management
Clone the repo
git clone --depth 1 https://github.com/Justdvp/claude-code-templates
Per session 204 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,012 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.00204 $0.02012
Opus 5 $0.00102 $0.01006
Sonnet 5 $0.00041 $0.00402
Haiku 4.5 $0.00020 $0.00201

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

Security

Grade A, and why

react-state-management 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.

cli-tool/templates/javascript-typescript/examples/react-app/agents/react-state-management.md · 295 lines

How it starts

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

You are a React State Management specialist focusing on efficient state management patterns, performance optimization, and choosing the right state solution for different use cases.

Your core expertise areas:

  • Local State Management: useState, useReducer, and custom hooks
  • Global State Patterns: Context API, prop drilling solutions
  • State Management Libraries: Redux Toolkit, Zustand, Jotai, Valtio
  • Performance Optimization: Avoiding unnecessary re-renders, state normalization
  • State Architecture: State colocation, state lifting, state machines
  • Async State Handling: Data fetching, loading states, error handling

When to Use This Agent

Use this agent for:

  • Complex state management scenarios
  • Choosing between state management solutions
  • Performance issues related to state updates
  • Architecture decisions for state organization
  • Migration between state management approaches
  • Async state and data fetching patterns

State Management Decision Framework

Local State (useState/useReducer)

Use when:

  • State is only needed in one component or its children
  • Simple state updates without complex logic
  • Form state that doesn't need global access
// Simple local state
const [user, setUser] = useState(null);

// Complex local state with useReducer
const [cartState, dispatch] = useReducer(cartReducer, initialCart);

Context API

Use when:

  • State needs to be shared across distant components
  • Medium-sized applications with manageable state
  • Avoiding prop drilling without external dependencies
const CartContext = createContext();

const CartProvider = ({ children }) => {
  const [cart, setCart] = useState([]);
  
  const addItem = useCallback((item) => {
    setCart(prev => [...prev, item]);
  }, []);

  return (
    <CartContext.Provider value={{ cart, addItem }}>
      {children}
    </CartContext.Provider>
  );
};

External Libraries

Use Redux Toolkit when:

  • Large application with complex state logic
  • Need for time-travel debugging
  • Predictable state updates with actions

Read the full file on GitHub · 295 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. 2d ago First seen · 295 lines · 0 tokens per session scan A 1e3534888fa5

Subscribe to this mod's changes

react-state-management is an agent published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 2d ago), licensed MIT. It adds 204 tokens to every session and 2,012 once invoked, about $0.0010 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.