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/content-sdkWrote 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/content-sdk/angular)<a href="https://agentmods.dev/rules/sitecore/content-sdk/angular"><img src="https://agentmods.dev/badge/rules/sitecore/content-sdk/angular/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/content-sdk/angular"><img src="https://agentmods.dev/badge/rules/sitecore/content-sdk/angular.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.00345 |
| Opus 5.5 | $0.00000 | $0.00138 |
| Sonnet 5.5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
angular 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 15d 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
Angular conventions
- Standalone components only — no
NgModulefeature pattern; declare dependencies inimports - Signals:
input()/input.required()for inputs,computed()for derived state,toSignal()for route data - Selectors:
appprefix, kebab-case for components, camelCase for directives - DI belongs here —
inject()is fine in components, providers and resolvers, but never insrc/content-sdk/ - Providers:
app.config.ts(browser) andapp.config.server.ts(addsprovideServerRendering+provideServerLoaderRunner).provideClientHydration()is intentionally omitted soRouterLinkattaches after bootstrap - Routes:
app.routes.tsandapp.routes.server.tsmust stay in sync (paths, render mode, HTTP status) - No server-only imports (
express,unstorage,node:*) anywhere undersrc/app/;process.envis unavailable in the browser — use the generatedenvironment*.ts - Templates:
@if/@forcontrol flow; Sitecore fields via*scText/*scRichText/*scImage/*scLink; placeholders via<sc-placeholder [name] [rendering]>
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.
- 15d ago First seen · 21 lines · 0 tokens per session scan A 2ad5a613828b
angular is a cursor rule published in the GitHub repository Sitecore/content-sdk (37 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 345 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-10-02.
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.