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 skills/kok-o/koko-contextos-agents/reactnpx skills add kok-o/koko-contextos-agents --skill reactgit clone --depth 1 https://github.com/kok-o/koko-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/koko-contextos-agents/react)<a href="https://agentmods.dev/skills/kok-o/koko-contextos-agents/react"><img src="https://agentmods.dev/badge/skills/kok-o/koko-contextos-agents/react.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.00031 | $0.01240 |
| Opus 5 | $0.00015 | $0.00620 |
| Sonnet 5 | $0.00006 | $0.00248 |
| Haiku 4.5 | $0.00003 | $0.00124 |
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 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 ships with it
5 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.
- 4d ago First seen · 133 lines · 31 tokens per session scan A 1b1fcb182288
React is a skill published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 1,240 once invoked, about $0.0002 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-31.
Other skills, from other repositories
rust-best-practices
Comprehensive Rust best practices covering ownership, error handling, async patterns, testing, and project structure.
cache_patterns
Instruction set for enabling and operating the Spring Cache abstraction in Spring Boot when implementing application-level caching for performance-sensitive workloads.
event_driven
Structure systems around asynchronous, event-based communication to decouple producers and consumers for improved scalability and resilience. Use when building loosely coupled systems with asynchronous message-based communication.
cache_patterns
Instruction set for enabling and operating the Spring Cache abstraction in Spring Boot when implementing application-level caching for performance-sensitive workloads.
event_driven
Structure systems around asynchronous, event-based communication to decouple producers and consumers for improved scalability and resilience. Use when building loosely coupled systems with asynchronous message-based communication.
universal-patterns
Use when implementing language-agnostic patterns like layered architecture, dependency injection, error handling, or code organization principles across any technology stack.