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 roedyrustam/vibes-plug --skill state-management-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/state-management-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/state-management-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/state-management-expert/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/roedyrustam/vibes-plug/state-management-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/state-management-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00077 | $0.02519 |
| Opus 5 | $0.00039 | $0.01260 |
| Sonnet 5 | $0.00015 | $0.00504 |
| Haiku 4.5 | $0.00008 | $0.00252 |
Grade A, and why
state-management-expert 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State Management Expert (Modern React Edition)
English
Orchestration & Integration
Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.
Description
Expert guide for selecting and implementing the right state management solution for React and Next.js applications. Covers Zustand 5, Jotai 2, Valtio, TanStack Store, and Redux Toolkit 2, with clear guidance on when to use each, proper separation of server state (TanStack Query) from client state, and advanced patterns like slices, persistence, and devtools integration.
Trigger Conditions
- Choosing a state management library for a new React/Next.js project.
- Refactoring prop drilling or complex Context API usage.
- Implementing global UI state (modals, drawers, theme, auth session).
- Managing complex form state across multiple steps.
- Implementing undo/redo, optimistic updates, or derived state.
- Migrating from Redux to a lighter alternative.
State Category Separation (Critical First Step)
Before choosing a library, categorize your state:
| Category | Description | Solution |
|---|---|---|
| Server State | Data from APIs, databases | TanStack Query / SWR |
| URL State | Route params, search filters | useSearchParams, nuqs |
| Form State | Input values, validation errors | React Hook Form + Zod |
| UI/Local State | Modals, drawers, toggles | useState / useReducer |
| Global Client State | Theme, auth, shopping cart | Zustand / Jotai |
| Cross-tab State | Sync across browser tabs | Zustand + BroadcastChannel |
Rule: Do NOT store server data in client state. Let TanStack Query own all async data.
Library Selection Guide
| Criteria | Zustand 5 | Jotai 2 | Valtio | Redux Toolkit |
|---|---|---|---|---|
| Mental Model | Single store, actions | Atomic, bottom-up | Proxy-based, mutable | Flux, reducers |
| Bundle Size | ~1KB | ~3KB | ~3KB | ~15KB+ |
| DevTools | Redux DevTools | Jotai DevTools | Redux DevTools | Built-in |
| Async | Manual or middleware | atomWithQuery |
snapshot |
createAsyncThunk |
| Best For | General global state | Atomic derived state | Simple mutable state | Large teams, strict patterns |
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 · 279 lines · 77 tokens per session scan A 6b8c50db7593
state-management-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (50 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 2,519 once invoked, about $0.0004 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-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. Use when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements. Do NOT use…
react-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes. Do NOT…
nextjs-code-review
A code-review assistant for Next.js applications. Next.js is a framework for building React websites and web applications, including pages that run on the server.
component-scaffold
Create a new React component with co-located test, story, and styles. Use when creating new UI components, when asked to scaffold/generate a component, or when building new pages.
expo
Expert in Expo for React Native development. Covers Expo Router, EAS Build and Submit, development builds, native module integration, and production deployment. Knows how to build cross-platform mobile apps efficiently while maintaining access to native capabilities. Use when "expo, react native, mobile app, eas…
frontend
World-class frontend engineering - React philosophy, performance, accessibility, and production-grade interfacesUse when "frontend, react, vue, svelte, next.js, nuxt, component, state management, redux, zustand, client side, spa, ssr, hydration, bundle size, web vitals, accessibility, a11y, responsive, css, tailwind…