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 rules/sitecore/xmcloud-starter-js/nextjsgit clone --depth 1 https://github.com/Sitecore/xmcloud-starter-jsWhat 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.00000 | $0.01315 |
| Opus 5 | $0.00000 | $0.00658 |
| Sonnet 5 | $0.00000 | $0.00263 |
| Haiku 4.5 | $0.00000 | $0.00131 |
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 2d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Development Patterns
Configuration
Next.js Config:
- Configure i18n for multi-language XM Cloud sites
- Set up proper image domains for XM Cloud media
- Implement rewrites for XM Cloud API routes
- Configure webpack for SCSS and other assets
- Set up proper build optimization
// next.config.js pattern
const nextConfig = {
i18n: {
locales: ['en', 'en-CA'],
defaultLocale: process.env.DEFAULT_LANGUAGE || 'en',
},
images: {
remotePatterns: [
{
protocol: 'https',
hostname: 'edge*.**',
},
{
protocol: 'https',
hostname: 'xmc-*.**',
},
],
},
async rewrites() {
return [
{
source: '/robots.txt',
destination: '/api/robots',
},
{
source: '/sitemap.xml',
destination: '/api/sitemap',
},
];
},
};
Environment Variables:
- Use NEXT_PUBLIC_ prefix for client-side variables
- Validate required environment variables at build time
- Use different .env files for different environments
- Never commit sensitive environment variables
App Router Pages and Routing
Catch-All Routes:
- Use
src/app/[site]/[locale]/[[...path]]/page.tsxfor XM Cloud page routing - Fetch layout data in the Server Component with
sitecore-client - Call
notFound()when the route does not exist - Use
draftMode()and editing search params for preview and Pages Editor
// page.tsx pattern (App Router)
export default async function Page({ params, searchParams }: PageProps) {
const { site, locale, path } = await params;
const draft = await draftMode();
let page;
if (draft.isEnabled) {
const editingParams = await searchParams;
page = await client.getPreview(editingParams);
} else {
page = await client.getPage(path ?? [], { site, locale });
}
if (!page) {
notFound();
}
return (/* Layout + Providers */);
}
Pages Router:
- Only
examples/basic-nextjs-pages-routerusessrc/pages/[[...path]].tsxwithgetStaticProps/getServerSideProps - Do not add Pages Router patterns to App Router starters
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.
- 2d ago First seen · 210 lines · 0 tokens per session scan A 37179514b13c
nextjs is a cursor rule published in the GitHub repository Sitecore/xmcloud-starter-js (29 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,315 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-08-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.