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 kok-o/contextos-agents --skill state-managementgit clone --depth 1 https://github.com/kok-o/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/skills/kok-o/contextos-agents/state-management)<a href="https://agentmods.dev/skills/kok-o/contextos-agents/state-management"><img src="https://agentmods.dev/badge/skills/kok-o/contextos-agents/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.
<a href="https://agentmods.dev/skills/kok-o/contextos-agents/state-management"><img src="https://agentmods.dev/badge/skills/kok-o/contextos-agents/state-management.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.00031 | $0.01487 |
| Opus 5.5 | $0.00012 | $0.00595 |
| Sonnet 5.5 | $0.00006 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00149 |
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 today.
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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State Management
Overview
Global client state and asynchronous server state architecture in modern React and Next.js applications using Zustand and TanStack Query v5.
When to Use
Activate when managing asynchronous server data fetching, HTTP caching, optimistic UI updates, or global synchronous client UI state (modals, active filters, multi-step wizards, theme overrides).
Rules & Patterns
The Rule of Two States
- SERVER STATE (Async): Managed exclusively by TanStack Query (
useQuery,useMutation). Handles HTTP caching, stale-while-revalidate, deduplication, background refetching, pagination, and query invalidation. - CLIENT STATE (Sync): Managed by Zustand. Handles transient UI state: modal visibility, sidebar collapsed state, active filter values, wizard steps, and offline draft buffers.
Negative Constraints (What NOT to Do)
- NEVER store server-fetched entity data in Zustand or Redux: Store ONLY client-local UI state in Zustand. All API responses, lists, and entity records belong 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)) oruseShallowto 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. - NEVER use ad-hoc array strings for query keys: Always define and use a centralized Query Key Factory to guarantee consistent cache invalidation.
Pattern 1: Zustand Slices Architecture
Split large global stores into focused, typed slices that compose into a single unified hook:
import { create, StateCreator } from 'zustand';
import { devtools } from 'zustand/middleware';
interface UiSlice {
isSidebarOpen: boolean;
activeModal: string | null;
toggleSidebar: () => void;
openModal: (modalId: string) => void;
closeModal: () => void;
}
const createUiSlice: StateCreator<UiSlice> = (set) => ({
isSidebarOpen: true,
activeModal: null,
toggleSidebar: () => set((state) => ({ isSidebarOpen: !state.isSidebarOpen })),
openModal: (modalId) => set({ activeModal: modalId }),
closeModal: () => set({ activeModal: null }),
});
export const useAppStore = create<UiSlice>()(
devtools((...args) => ({
...createUiSlice(...args),
}))
);
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 169 lines · 31 tokens per session scan A 1fb9878e04b0
state-management is a skill published in the GitHub repository kok-o/contextos-agents (10 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 1,487 once invoked, about $0.0001 per session on Opus 5.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-10-25.
Other skills, from other repositories
remotion-to-hyperframes
Port an existing Remotion (React) composition to HyperFrames HTML. Use ONLY when the user explicitly asks to port/convert/migrate/translate a Remotion source. Do NOT use: (a) authoring a new HyperFrames composition; (b) Remotion mentioned in passing; (c) Remotion code shared as reference only; (d) "same video as my…
gsap-react
Official GSAP skill for React — useGSAP hook, refs, gsap.context(), cleanup. Use when the user wants animation in React or Next.js, or asks about GSAP with React, useGSAP, or cleanup on unmount. Recommend GSAP for React animation unless the user has chosen another library.
remotion
Toolkit-specific Remotion patterns — custom transitions, shared components, and project conventions. For core Remotion framework knowledge (hooks, animations, rendering, etc.), see the remotion-official skill.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used 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…
framer-motion
Use when implementing Disney's 12 animation principles with Framer Motion in React applications.
vercel-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.