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.
git clone --depth 1 https://github.com/blockmatic/basilicWrote 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/rules/blockmatic/basilic/nextjs)<a href="https://agentmods.dev/rules/blockmatic/basilic/nextjs"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/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/rules/blockmatic/basilic/nextjs"><img src="https://agentmods.dev/badge/rules/blockmatic/basilic/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.00000 | $0.00285 |
| Opus 5.5 | $0.00000 | $0.00114 |
| Sonnet 5.5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
nextjs 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
Route Collocation
Keep route-specific files collocated with their route segment. Place page components, section components, and route-specific utilities inside the same directory as the route's page.tsx.
app/(dashboard)/settings/security/page.tsx→ collocatesecurity-section.tsx,api-keys-card.tsx, etc. insettings/security/- ❌
settings/security-section.tsxwhen the page lives insettings/security/
React Server Components (CRITICAL)
ALWAYS default to Server Components. Only 'use client' when necessary: interactive features (onClick/onChange/onSubmit), Browser APIs (window/document/localStorage), React hooks (useState/useEffect/useContext), client-side libraries, event listeners
❌ Unnecessary client components, entire page as client
Performance Optimization
See @.cursor/rules/frontend/react.mdc for concurrent rendering (Suspense/Transitions/Deferred Values)
Core Web Vitals & Images
Optimize Core Web Vitals (LCP <2.5s, FID <100ms, CLS <0.1), images (WebP, proper sizes, lazy loading)
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 · 23 lines · 0 tokens per session scan A 9b5b50c6becc
nextjs is a cursor rule published in the GitHub repository blockmatic/basilic (90 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 285 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-09-03.
Other cursor rules, from other repositories
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
react-chakra-ui---typescript-usage
Guidance for using TypeScript with Chakra UI components in React. It covers typed component props, custom themes, editor support, and avoiding the unsafe any type.
05-web-development
Use the following format for code blocks.
hatch3r-component-conventions
Component structure, styling tokens, loading/error/empty states, form validation timing, and accessible label patterns for Vue, React, and JSX.
aphrodite
Frontend specialist — React 19, TypeScript strict, WCAG accessibility, responsive design, TDD, modern API patterns, deprecated npm detection. Calls apollo for discovery, sends to themis for review.