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/kok-o/koko-contextos-agents/reactgit clone --depth 1 https://github.com/kok-o/koko-contextos-agentsWhat 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.00000 | $0.01788 |
| Opus 5 | $0.00000 | $0.00894 |
| Sonnet 5 | $0.00000 | $0.00358 |
| Haiku 4.5 | $0.00000 | $0.00179 |
Grade A, and why
react 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 yesterday.
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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: React
React Engineering & Performance Best Practices
Overview
Enforces declarative, component-driven UI architecture with optimal re-render cycles, state colocation, responsive optimistic updates, and robust accessibility standards.
When to Use
Activate whenever creating, refactoring, or optimizing React functional components, custom hooks, context providers, or UI interaction states.
Negative Constraints (What NOT to Do)
- NEVER use
useEffectto synchronize or compute derived state: Calculate derived state inline during render. UseuseMemoonly for computationally intensive derivations. - NEVER use array indices as
keyprops on dynamic or reorderable lists: Always use stable, unique entity identifiers (item.id). - NEVER mutate React state directly: Always return new immutable references (
[...prev, newItem]or{ ...prev, key: value }). - NEVER declare subcomponents inside the render body of parent components: Declare components at module scope or in dedicated files to prevent DOM node remounting and lost focus state.
- NEVER create memory leaks in
useEffect: Always provide clean-up functions for event listeners,AbortController, timers, and websocket subscriptions. - NEVER lift state higher than necessary: Colocate state to the nearest common ancestor or leaf component to prevent wasteful re-renders of unrelated subtrees.
Rules & Patterns
1. State Colocation & Re-render Optimization
- State Colocation: Keep state as close as possible to the components that consume it.
- Composition to Prevent Re-renders: Pass expensive static subtrees as
childrento wrapper components holding state so the children do not re-render when the wrapper updates.
export function ExpandableCard({ title, children }: { title: string; children: React.ReactNode }) {
const [isOpen, setIsOpen] = useState(false);
return (
<div className="rounded-xl border p-4">
<button
type="button"
onClick={() => setIsOpen(v => !v)}
className="flex w-full justify-between font-semibold"
aria-expanded={isOpen}
>
<span>{title}</span>
<span>{isOpen ? '−' : '+'}</span>
</button>
{isOpen && <div className="mt-3 pt-3 border-t">{children}</div>}
</div>
);
}
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.
- yesterday First seen · 216 lines · 0 tokens per session scan A 8ff5cbb64d1d
react is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,788 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-08-31.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
core
Read .apc/manifest.md first. If it contains placeholders and the user requests initialization, follow .apc/init.md. If the task concerns APC itself, edit prompt source without filling consumer placeholders. Otherwise follow .apc/workflow.md §0 or §1.
unity-performance
Cursor rule "unity-performance" from Common-ka/ai-agent-unity-rules, covering unity performance rules, update/fixedupdate/lateupdate, usage rules, object pooling (unityengine.pool) and addressables (not resources).
react-composition-patterns
React composition patterns for scalable component architecture including compound components, context providers, state management, boolean prop alternatives, render props vs children, and React 19 API changes. Use when refactoring components with many boolean props, building component libraries, designing flexible…
react-rerender-optimization
React re-render optimization patterns including memo, useMemo, useCallback, useState, useRef, and derived state. Use when components re-render too often, dealing with stale closures, dependency arrays, performance issues, or optimizing slow components.
index
This project uses Unity 6.2 (LTS 2025) with modern systems and architectural approaches.