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/swesmith/davila7__claude-code-templates.734b8a50/react-state-managementgit clone --depth 1 https://github.com/swesmith/davila7__claude-code-templates.734b8a50Wrote 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/swesmith/davila7__claude-code-templates.734b8a50/react-state-management)<a href="https://agentmods.dev/agents/swesmith/davila7__claude-code-templates.734b8a50/react-state-management"><img src="https://agentmods.dev/badge/agents/swesmith/davila7__claude-code-templates.734b8a50/react-state-management.svg" alt="Measured on agentmods" 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.00204 | $0.02012 |
| Opus 5 | $0.00102 | $0.01006 |
| Sonnet 5 | $0.00041 | $0.00402 |
| Haiku 4.5 | $0.00020 | $0.00201 |
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.
This is a copy
100% identical to react-state-management — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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
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 · 295 lines · 0 tokens per session scan A 1e3534888fa5
react-state-management is an agent published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 8mo 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. It is 100% identical to react-state-management, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
tauri-axum-parity-checker
Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.