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 usrrname/cursorrules --skill nextjsgit clone --depth 1 https://github.com/usrrname/cursorrulesWrote 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/usrrname/cursorrules/nextjs)<a href="https://agentmods.dev/skills/usrrname/cursorrules/nextjs"><img src="https://agentmods.dev/badge/skills/usrrname/cursorrules/nextjs/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/usrrname/cursorrules/nextjs"><img src="https://agentmods.dev/badge/skills/usrrname/cursorrules/nextjs.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.00014 | $0.00414 |
| Opus 5.5 | $0.00006 | $0.00166 |
| Sonnet 5.5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
nextjs-react19 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 1mo 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.
What it actually says
Next.js React 19 Skill
Build modern Next.js applications with App Router and React 19 features.
When to Use
- Creating Next.js pages and layouts
- Working with Server Components
- Implementing data fetching
- Setting up API routes
Critical Rules
App Router
- Use Server Components by default
- Mark Client Components with 'use client'
- Keep Client Components small and focused
- Use async/await in Server Components
Data Fetching
- Fetch directly in Server Components
- Use React.cache for deduplication
- Implement proper error boundaries
- Use loading.js for suspense states
Routing
- Use file-based routing in app/
- Implement parallel routes with @folder
- Use intercepting routes for modals
- Handle dynamic segments with [param]
React 19 Features
- Use Actions for form mutations
- Leverage useOptimistic for UI updates
- Implement useFormStatus for pending states
- Use Server Actions for mutations
Examples
Good
// Server Component
async function BlogPage() {
const posts = await getPosts();
return (
<main>
{posts.map(post => (
<PostCard key={post.id} post={post} />
))}
</main>
);
}
// Client Component
'use client';
function LikeButton({ postId }: { postId: string }) {
const [optimisticLikes, addOptimisticLike] = useOptimistic(
likes,
(state) => state + 1
);
return <button>{optimisticLikes} likes</button>;
}
Related
/react- React TypeScript patterns/typescript- TypeScript fundamentals
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.
- 1mo ago First seen · 81 lines · 14 tokens per session scan A 2aea92026abc
nextjs-react19 is a skill published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It adds 14 tokens to every session and 414 once invoked, about $0.0001 per session on Opus 5.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
front-vitest
Depth for Vitest tests of front- React 19 SPAs when DOM, RTL, TanStack Query hooks, or TanStack Router route-tree tests are needed. USE WHEN: adding jsdom or testing-library, writing tsx render or renderHook tests, testing createMemoryHistory plus RouterProvider, Suspense UI, or React 19 act fixtures. DO NOT USE WHEN…
component-creation
Step-by-step workflow for creating accessible, tested UI components. Use when the user asks to create a new UI component.
state-management
Workflow for choosing and implementing the right state management approach. Use when the user needs to manage state for a new feature or refactor.
tanstack-query-setup
Implements TanStack Query (React Query) for server state management with caching, mutations, optimistic updates, and infinite queries. Use when users request "react query", "tanstack query", "data fetching", "cache management", or "server state".
eslint-prettier-config
Configures ESLint and Prettier for consistent code quality with TypeScript, React, and modern best practices. Use when users request "ESLint setup", "Prettier config", "linting configuration", "code formatting", or "lint rules".
storybook-setup
Sets up Storybook for component documentation with controls, actions, accessibility testing, and visual regression. Use when users request "Storybook setup", "component documentation", "UI library", "component stories", or "design system docs".