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/Sitecore/xmcloud-starter-jsWrote 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/sitecore/xmcloud-starter-js/project-context)<a href="https://agentmods.dev/rules/sitecore/xmcloud-starter-js/project-context"><img src="https://agentmods.dev/badge/rules/sitecore/xmcloud-starter-js/project-context/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/sitecore/xmcloud-starter-js/project-context"><img src="https://agentmods.dev/badge/rules/sitecore/xmcloud-starter-js/project-context.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.01743 | $0.01743 |
| Opus 5.5 | $0.00697 | $0.00697 |
| Sonnet 5.5 | $0.00349 | $0.00349 |
| Haiku 4.5 | $0.00174 | $0.00174 |
Grade A, and why
project-context 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 7d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context
Repository Overview
This is the XM Cloud Front End Application Starter Kits repository containing multiple Next.js starter applications and SPA examples for Sitecore XM Cloud development.
Repository Structure:
/examples/- Contains starter front-end applications (Next.js and Angular)/authoring/- Sitecore content items, templates, and deployment configurations/local-containers/- Docker setup for local development environmentsxmcloud.build.json- Primary configuration for XM Cloud deployment
Starter Applications
Available Examples:
basic-nextjs- Simple Next.js starter with basic XM Cloud integration (App Router)basic-nextjs-pages-router- Minimal Pages Router baseline for legacy patternskit-nextjs-article-starter- Solterra & Co. - Editorial-style template for lifestyle brandskit-nextjs-location-finder- Alaris - Car brand template with location finder functionalitykit-nextjs-product-listing- SYNC - Product-focused template for audio gear companieskit-nextjs-skate-park- Simple demo site showcasing component exampleskit-angular-skate-park- Angular starter kit built on the Sitecore Content SDK for Angular, with server-side rendering (SSR)
Each starter demonstrates:
- Tailwind-based styling with Shadcn/ui components
- Personalized homepage via URL parameters
- Modular component architecture with variants
- Localization support for English (en) and Canadian English (en-CA)
Technology Stack
Core Technologies:
- Next.js 14+ - React framework with App Router (all starters except
basic-nextjs-pages-router) - TypeScript - Strict type safety throughout all components
- Sitecore XM Cloud - Headless content management and delivery
- Sitecore Content SDK - Modern SDK for XM Cloud integration
- Tailwind CSS - Utility-first CSS with container queries (@container)
- Shadcn/ui - Modern component library with accessibility features
Additional Libraries:
- Framer Motion - Animation library for interactive components
- Lucide React - Icon library for consistent iconography
- next-localization - Internationalization with dictionary support
- change-case - String case transformation utilities
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.
- 7d ago Changed · +14 tokens per session 95d6c6472ee7
- 1mo ago First seen · 154 lines · 1,729 tokens per session scan A 09550c68cd97
project-context is a cursor rule published in the GitHub repository Sitecore/xmcloud-starter-js (31 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,743 tokens to every session, about $0.0070 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.