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 skills add OpenLAIR/OpenSkill --skill evo-nextjs-render-optimizationgit clone --depth 1 https://github.com/OpenLAIR/OpenSkillWrote 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/openlair/openskill/evo-nextjs-render-optimization)<a href="https://agentmods.dev/skills/openlair/openskill/evo-nextjs-render-optimization"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-nextjs-render-optimization/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/openlair/openskill/evo-nextjs-render-optimization"><img src="https://agentmods.dev/badge/skills/openlair/openskill/evo-nextjs-render-optimization.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.00336 |
| Opus 5 | $0.00018 | $0.00168 |
| Sonnet 5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
evo-nextjs-render-optimization 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.
What it actually says
evo-nextjs-render-optimization
Optimizes React rendering by:
- Wrapping frequently re-rendered components in React.memo
- Adding useMemo for expensive computations
- Adding useCallback for callback stability
- Splitting overloaded contexts
Key Patterns
React.memo for ProductCard
Anti-pattern:
export function ProductCard({ product, onAddToCart, isInCart }: Props) { ... }
Fix:
import { memo } from 'react';
export const ProductCard = memo(function ProductCard({ product, onAddToCart, isInCart }: Props) { ... });
useMemo for expensive computations
const filteredProducts = useMemo(() =>
products.filter(...).sort(...),
[products, filter, sortBy]
);
useCallback for callbacks
const handleAddToCart = useCallback((id: string) => {
setCart(prev => [...prev, id]);
}, []);
Usage
import sys
sys.path.insert(0, '/app/environment/skills/evo-nextjs-render-optimization/scripts')
from utils import wrap_component_in_memo, add_usememo_to_computations, apply_render_fixes
wrap_component_in_memo('/app/src/components/ProductCard.tsx', 'ProductCard')
apply_render_fixes('/app/src/components/ProductList.tsx')
What ships with it
1 file 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.
- yesterday First seen · 53 lines · 36 tokens per session scan A b07018379338
evo-nextjs-render-optimization is a skill published in the GitHub repository OpenLAIR/OpenSkill (90 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 336 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-09-11.
Other skills, from other repositories
Cursor rules for building custom frontends with Momen
Cursor rules for building custom frontends with Momen.app as headless BaaS with GraphQL API, actionflows, AI agents, and Stripe integration.
Cursor rules for Next
Cursor rules for Next.js development with Vercel and TypeScript integration.
Next.js App Patterns
Use this skill when working in a Next.js App Router codebase (Next.js 14+) and you need safe patterns for server vs client components, data fetching, routing, and deployment without introducing hydration bugs or accidental client bundles.
React Component Patterns
Use this skill when you’re building or refactoring React components in a production app and want consistent patterns for typing, composition, state, and performance without introducing premature abstraction.
27 architecture rules preventing AI hallucinations: insecure auth (getSession vs
27 architecture rules preventing AI hallucinations: insecure auth (getSession vs getUser), synchronous params, deprecated imports, missing RLS, and Stripe key exposure. Built for Cursor Agent and Claude Code.
Cursor rules for Next
Cursor rules for Next.js development with React 19, Vercel AI, and Tailwind CSS integration.