state-management

state-management is a command for Claude Code from swesmith/davila7__claude-code-templates.734b8a50. It costs 0 tokens per session (371 once invoked), scanned A, a copy of state-management, MIT.

A command for adding or improving state management in an application, including stores, providers, and typed hooks.

In plain words
What is it for?
Use it to set up Context API, Redux Toolkit, Zustand, or custom hooks, with TypeScript types, middleware, loading and error states, and tests.
Why use it?
It helps select and connect an appropriate approach for shared data instead of letting state logic become scattered across components.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to set up Context API, Redux Toolkit, Zustand, or custom hooks, with TypeScript types, middleware, loading and error states, and tests.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/swesmith/davila7__claude-code-templates.734b8a50/state-management
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/swesmith/davila7__claude-code-templates.734b8a50

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/state-management/github.svg)](https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/state-management)
Your own site
<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/state-management"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/state-management/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 state-management

Your own site · 80×15
<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/state-management"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/state-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 371 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 100% copy Near-identical to another mod 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.00000 $0.00371
Opus 5 $0.00000 $0.00186
Sonnet 5 $0.00000 $0.00074
Haiku 4.5 $0.00000 $0.00037

Measured 5d ago against content hash 473be148b662, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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 5d 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.

Origin

This is a copy

100% identical to 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.

cli-tool/templates/javascript-typescript/examples/react-app/.claude/commands/state-management.md · 45 lines

What it actually says

React State Management

Implement state management solution for $ARGUMENTS following project conventions.

Task

Set up or optimize state management based on the requirements:

  1. Analyze current setup: Check existing state management approach and project structure
  2. Determine solution: Based on requirements, choose appropriate state management:
    • Context API for simple, localized state
    • Redux Toolkit for complex, global state
    • Zustand for lightweight global state
    • Custom hooks for component-level state
  3. Examine dependencies: Check package.json for existing state management libraries
  4. Implement solution: Create store, providers, and hooks with proper TypeScript types
  5. Set up middleware: Add devtools, persistence, or other middleware as needed
  6. Create typed hooks: Generate properly typed selectors and dispatch hooks
  7. Add tests: Write unit tests for state logic and reducers
  8. Update providers: Integrate with app's provider hierarchy

Implementation Requirements

  • Follow project's TypeScript conventions
  • Use existing state management patterns if present
  • Create proper type definitions for state shape
  • Include error handling and loading states
  • Add proper debugging setup (devtools)
  • Consider performance optimizations (selectors, memoization)

State Management Selection Guide

Choose based on complexity:

  • Simple state: React hooks + Context API
  • Medium complexity: Zustand or custom hooks
  • Complex state: Redux Toolkit with RTK Query
  • Form state: React Hook Form or Formik

Important Notes

  • ALWAYS check existing state management first
  • Don't install new dependencies without asking
  • Follow project's folder structure for state files
  • Consider server state vs client state separation
  • Add proper TypeScript types for all state interfaces
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. 5d ago First seen · 45 lines · 0 tokens per session scan A 473be148b662

Subscribe to this mod's changes

state-management is a command published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 371 tokens. A static security scan graded it A with 0 findings. It is 100% identical to state-management, differing in 0 lines, and is treated as a copy.