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 skills add mickeyyaya/refactoring-skills --skill state-management-patternsgit clone --depth 1 https://github.com/mickeyyaya/refactoring-skillsWrote 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/skills/mickeyyaya/refactoring-skills/state-management-patterns)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/state-management-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/state-management-patterns/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.
<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/state-management-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/state-management-patterns.svg" alt="Reviewed on agentmods" width="80" 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.00090 | $0.05436 |
| Opus 5 | $0.00045 | $0.02718 |
| Sonnet 5 | $0.00018 | $0.01087 |
| Haiku 4.5 | $0.00009 | $0.00544 |
Grade A, and why
state-management-patterns 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 9d 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 — 557 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State Management Patterns
Overview
Mismanaged state is the root cause of most UI bugs, stale data issues, and security vulnerabilities in web applications. Uncoordinated mutations lead to race conditions, inconsistent UIs, and hard-to-reproduce bugs. Use this guide when designing new state architecture, reviewing pull requests that touch shared state, or diagnosing unexpected re-renders and data consistency issues.
When to use: Designing client or server state architecture; reviewing Redux/Zustand/Context code; evaluating server-state caching strategies; auditing session and authentication implementations; diagnosing UI inconsistency bugs.
Quick Reference
| Pattern | Core Idea | Primary Red Flag |
|---|---|---|
| Flux/Redux Unidirectional | Single store, actions → reducer → new state | Mutating state directly, actions with side effects in reducers |
| Server State (React Query/SWR) | Cache remote data separately from UI state | Manually managing loading/error booleans for every fetch |
| Optimistic Updates | Apply change immediately, rollback on failure | No rollback path, no error handling after mutation |
| Finite State Machines | Explicit states and transitions (XState) | Boolean flag explosion, impossible state combinations |
| Session Management | Secure cookie or JWT with proper flags | Missing HttpOnly/Secure flags, session fixation on login |
| Distributed Session Stores | Redis or DB-backed sessions for multi-instance apps | In-memory sessions break with multiple server instances |
| Derived State & Selectors | Compute from source of truth, memoize expensive derivations | Duplicating state that could be derived, missing memoization |
| Anti-Patterns | Global state abuse, prop drilling, state duplication | Everything in a global store, deeply nested prop chains |
Patterns in Detail
1. Flux/Redux Unidirectional Data Flow
The core insight of Flux and Redux is that state flows in one direction: action → reducer → store → view. Views dispatch actions; they never mutate state directly.
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.
- 9d ago First seen · 557 lines · 90 tokens per session scan A b18f67b35885
state-management-patterns is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 90 tokens to every session and 5,436 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
fuzzy-ranking
Rank fuzzy matches with rankItem, filter with RankingInfo.passed, compare saved ranking metadata with compareItems, and configure rankings, thresholds, accessors, min/max bounds, or diacritics. Load for @tanstack/match-sorter-utils itself or fuzzy Table filterMeta wiring.
api-not-found
Diagnose missing TanStack Table v9 exports, options, state slices, and instance methods. Load before inventing an API when code sees a type error, undefined feature method, absent object key, adapter mismatch, or v8-shaped example.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.