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/omergulcicek/omergulcicek.com/state-managementgit clone --depth 1 https://github.com/omergulcicek/omergulcicek.comWrote 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/omergulcicek/omergulcicek.com/state-management)<a href="https://agentmods.dev/rules/omergulcicek/omergulcicek.com/state-management"><img src="https://agentmods.dev/badge/rules/omergulcicek/omergulcicek.com/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.00000 | $0.00310 |
| Opus 5 | $0.00000 | $0.00155 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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 4d 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.
What it actually says
State Management
Constraints
- Library: Use
Zustandfor client state. - Scope: Define Global state in
src/stores, Feature state insrc/features/[feature]/stores. - Selectors: Always consume state via selectors (
useStore(s => s.val)). - SSR: Guarantee client-side rendering with
useHydrated. - Persistence: Configure
onRehydrateStoragewhen usingpersistmiddleware. - Server State: Use TanStack Query. Do not store server data in the global store.
Bans
- Passing store data via props.
- Storing high-frequency state (e.g., inputs) in the store.
- Executing side-effects (API calls) inside the store.
- Accessing
window/localStorageduring initialization. - Returning the entire store without selectors.
Correct Implementation
Incorrect Implementation
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.
- 4d ago First seen · 43 lines · 0 tokens per session scan A 08ef0e37b2cf
state-management is a cursor rule published in the GitHub repository omergulcicek/omergulcicek.com (15 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 310 tokens. 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-01.
Other cursor rules, from other repositories
agent-development
Python agents are typically in folders named agent-py/ or agent/ and use the sdk-python/ package.
development-workflow
CopilotKit uses a monorepo structure with.
quick-reference
Cursor rule "quick-reference" from CopilotKit/CopilotKit, covering copilotkit quick reference, need to...?, build a simple copilot, create multi-agent systems and integrate with crewai.
cursorrules
Cursor rule "cursorrules" from CopilotKit/CopilotKit, covering instructions, additional command options and notes.
js-and-ts
When writing JavaScript or TypeScript code, use this guide for JavaScript best practices and guidance.
jsx-and-tsx
When writing React code, use this guide for React best practices and guidance.