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/panpanfr/oh-my-kilo/vercel-reactnpx skills add PanPanFR/oh-my-kilo --skill vercel-reactgit clone --depth 1 https://github.com/PanPanFR/oh-my-kiloWrote 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/panpanfr/oh-my-kilo/vercel-react)<a href="https://agentmods.dev/skills/panpanfr/oh-my-kilo/vercel-react"><img src="https://agentmods.dev/badge/skills/panpanfr/oh-my-kilo/vercel-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.1 | $0.00073 | $0.02766 |
| Opus 5 | $0.00036 | $0.01383 |
| Sonnet 5 | $0.00015 | $0.00553 |
| Haiku 4.5 | $0.00007 | $0.00277 |
Grade A, and why
vercel-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 5d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vercel React Best Practices + Composition Patterns
Unified skill combining performance rules (70+) with composition architecture patterns.
When to Apply
- Writing new React components or Next.js pages
- Implementing data fetching (client/server)
- Reviewing code for performance issues
- Refactoring existing React/Next.js code
- Optimizing bundle size or load times
- Designing component APIs (avoid boolean prop proliferation)
- Building reusable component libraries
PART 1: PERFORMANCE RULES (Priority Order)
1. Eliminating Waterfalls (CRITICAL)
| Rule | Description |
|---|---|
async-cheap-condition-before-await |
Check cheap sync conditions before awaiting flags |
async-defer-await |
Move await into branches where actually used |
async-parallel |
Use Promise.all() for independent operations |
async-dependencies |
Use better-all for partial dependencies |
async-api-routes |
Start promises early, await late in API routes |
async-suspense-boundaries |
Use Suspense to stream content |
Key pattern: Start promises before awaiting, use Promise.all() or better-all for parallelism.
2. Bundle Size Optimization (CRITICAL)
| Rule | Description |
|---|---|
bundle-barrel-imports |
Import directly, avoid barrel files (lucide-react, MUI, etc.) |
bundle-analyzable-paths |
Prefer statically analyzable import paths |
bundle-dynamic-imports |
Use next/dynamic for heavy components |
bundle-defer-third-party |
Load analytics/logging after hydration |
bundle-conditional |
Load modules only when feature activated |
bundle-preload |
Preload on hover/focus for perceived speed |
Quick wins:
// ❌ Barrel import - loads 1500+ modules
import { Check, X } from 'lucide-react'
// ✅ Direct import (Next.js 13.5+ transforms automatically)
// ✅ Non-Next.js: import Check from 'lucide-react/dist/esm/icons/check'
3. Server-Side Performance (HIGH)
| Rule | Description |
|---|---|
server-auth-actions |
Authenticate inside Server Actions (not just middleware) |
server-cache-react |
Use React.cache() for per-request deduplication |
server-cache-lru |
Use LRU cache for cross-request caching |
server-dedup-props |
Avoid duplicate serialization in RSC props |
server-hoist-static-io |
Hoist static I/O (fonts, logos) to module level |
server-no-shared-module-state |
No mutable module-level request state |
server-serialization |
Minimize data passed to client components |
server-parallel-fetching |
Restructure components to parallelize fetches |
server-parallel-nested-fetching |
Chain nested fetches per item in Promise.all |
server-after-nonblocking |
Use after() for non-blocking operations |
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.
- 5d ago First seen · 310 lines · 0 tokens per session scan A f4e475f01044
vercel-react is a skill published in the GitHub repository PanPanFR/oh-my-kilo (11 stars, last pushed 13d ago), licensed MIT. It adds 73 tokens to every session and 2,766 once invoked, about $0.0004 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 skills, from other repositories
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.