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 rules/kok-o/koko-contextos-agents/state-managementgit clone --depth 1 https://github.com/kok-o/koko-contextos-agentsWrote 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/rules/kok-o/koko-contextos-agents/state-management)<a href="https://agentmods.dev/rules/kok-o/koko-contextos-agents/state-management"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/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.00028 | $0.01068 |
| Opus 5 | $0.00014 | $0.00534 |
| Sonnet 5 | $0.00006 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: state-management
State Management
Overview
Global client state and server state management in modern React and Next.js applications using Zustand and TanStack Query.
When to Use
Activate when managing asynchronous server data fetching/caching, optimistic UI updates, or global UI client state (modals, filters, wizards).
Rules & Patterns
The Rule of Two States
- SERVER STATE (Async): Managed exclusively by TanStack Query (
useQuery,useMutation). Caching, background refetching, pagination, and invalidation. - CLIENT STATE (Sync): Managed by Zustand. Modal visibility, active filters, wizard step, theme.
Negative Constraints (What NOT to Do)
- NEVER store server-fetched data in Zustand or Redux stores: Store ONLY client-local UI state in Zustand. All API data belongs in TanStack Query.
- NEVER duplicate derived state: Compute values inline or via
useMemofrom existing state instead of storing redundant state variables. - NEVER subscribe to entire store objects in components: Always use atomic selector functions (e.g.
useStore(state => state.isOpen)) to prevent unnecessary component re-renders. - NEVER mutate state directly: Always return new immutable state objects in Zustand setters.
- NEVER ignore optimistic rollback on mutation failure: When implementing optimistic UI, always capture
previousDatainonMutateand restore it inonError.
Code Examples
See EXAMPLES.md for Zustand store patterns and optimistic TanStack mutations.
Validation Checklist
- Clear separation between Server (TanStack Query) and Client (Zustand) state
- Atomic selectors used on all Zustand hook calls
- Optimistic updates implement rollback on error
- Zero duplicated derived state
Common Mistakes
- Subscribing to full store objects causing cascading re-renders. See
TROUBLESHOOTING.md.
Integration Notes
Interacts with react, nextjs, and typescript.
State Management Examples — Anti-patterns vs ContextOS Standard
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.
- 6d ago First seen · 129 lines · 28 tokens per session scan A 1c493ba080d1
state-management is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 1,068 once invoked, about $0.0001 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.
Other cursor rules, from other repositories
hatch3r-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
react-composition-patterns
React composition patterns for scalable component architecture including compound components, context providers, state management, boolean prop alternatives, render props vs children, and React 19 API changes. Use when refactoring components with many boolean props, building component libraries, designing flexible…
react-javascript-performance
JavaScript performance micro-optimizations for React applications including loops, caching, data structures, Set/Map lookups, array methods, RegExp hoisting, and immutable operations. Use when optimizing hot paths, working with arrays, loops, caching, or data structure lookups.
react-rerender-optimization
React re-render optimization patterns including memo, useMemo, useCallback, useState, useRef, and derived state. Use when components re-render too often, dealing with stale closures, dependency arrays, performance issues, or optimizing slow components.
react-performance-critical
Critical React performance patterns for eliminating async waterfalls and optimizing bundle size. Use when dealing with slow loading, Promise.all, async/await parallelization, bundle size optimization, lazy loading, code splitting, barrel file imports, or tree shaking issues.
react-rendering-performance
React rendering and DOM performance patterns for animations, SVG optimization, CSS content-visibility, conditional rendering, and useTransition loading states. Use when working with animations, SVG elements, long lists, show/hide toggles, or loading state management.