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/innei-template/smart-webapp-template/state-managementgit clone --depth 1 https://github.com/innei-template/smart-webapp-templateWrote 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/innei-template/smart-webapp-template/state-management)<a href="https://agentmods.dev/rules/innei-template/smart-webapp-template/state-management"><img src="https://agentmods.dev/badge/rules/innei-template/smart-webapp-template/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 | $0.00008 | $0.00755 |
| Opus 5 | $0.00004 | $0.00378 |
| Sonnet 5 | $0.00002 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00076 |
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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State Management with Jotai
This project uses Jotai for state management with custom utilities and patterns.
Core Setup
Global Store: Use jotaiStore from src/lib/jotai.ts
import { jotaiStore } from '~/lib/jotai'
Custom Hook Utility: Use createAtomHooks for consistent atom patterns
import { createAtomHooks } from '~/lib/jotai'
const [useMyAtom, useSetMyAtom, useMyAtomValue, myAtom] = createAtomHooks(atom(null))
Atom Organization
Atom Location: Store atoms in src/atoms/ directory
// File: src/atoms/user.ts
import { atom } from 'jotai'
export const userAtom = atom(null)
export const isLoggedInAtom = atom((get) => get(userAtom) !== null)
Usage Patterns
Reading State:
import { useAtomValue } from 'jotai'
import { userAtom } from '~/atoms/user'
function UserProfile() {
const user = useAtomValue(userAtom)
return <div>{user?.name}</div>
}
Writing State:
import { useSetAtom } from 'jotai'
import { userAtom } from '~/atoms/user'
function LoginForm() {
const setUser = useSetAtom(userAtom)
const handleLogin = (userData) => {
setUser(userData)
}
}
Reading and Writing:
import { useAtom } from 'jotai'
import { userAtom } from '~/atoms/user'
function UserSettings() {
const [user, setUser] = useAtom(userAtom)
const updateUser = (updates) => {
setUser({ ...user, ...updates })
}
}
Advanced Patterns
Derived Atoms:
import { atom } from 'jotai'
const countAtom = atom(0)
const doubledAtom = atom((get) => get(countAtom) * 2)
Async Atoms:
const userIdAtom = atom(1)
const userAtom = atom(async (get) => {
const userId = get(userIdAtom)
return fetchUser(userId)
})
Write-Only Atoms:
const writeOnlyAtom = atom(
null, // no read function
(get, set, newValue) => {
// write logic
set(someOtherAtom, newValue)
}
)
Provider Setup
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 · 123 lines · 8 tokens per session scan A 48a97b128dbd
state-management is a cursor rule published in the GitHub repository innei-template/smart-webapp-template (142 stars, last pushed 8d ago), licensed MIT. It adds 8 tokens to every session and 755 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.