What is content-sdk-component-data-strategy?

Guidance for how Angular components receive Sitecore content, including page data, shared context, and placeholder inputs. A placeholder is a page area where Sitecore chooses which component to render.

Use it when passing fields to mapped components, adding page-level loaders, reading route data, or accessing the current Sitecore page context.

It prevents components from fetching the same page data in competing ways and avoids data disappearing after client-side navigation.

content-sdk-component-data-strategy — Skill by Sitecore/content-sdk

Install

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.

Any agent

npx skills add Sitecore/content-sdk --skill content-sdk-component-data-strategy

Clone the repo

git clone --depth 1 https://github.com/Sitecore/content-sdk

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sitecore/content-sdk/content-sdk-component-data-strategy/github.svg)](https://agentmods.dev/skills/sitecore/content-sdk/content-sdk-component-data-strategy)

Your own site

<a href="https://agentmods.dev/skills/sitecore/content-sdk/content-sdk-component-data-strategy"><img src="https://agentmods.dev/badge/skills/sitecore/content-sdk/content-sdk-component-data-strategy/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sitecore/content-sdk/content-sdk-component-data-strategy"><img src="https://agentmods.dev/badge/skills/sitecore/content-sdk/content-sdk-component-data-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 327 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00027	$0.00327
Opus 5.5	$0.00011	$0.00131
Sonnet 5.5	$0.00005	$0.00065
Haiku 4.5	$0.00003	$0.00033

Measured 15d ago against content hash dc411c723b09, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

content-sdk-component-data-strategy 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.

packages/create-content-sdk-app/src/templates/angular/.agents/skills/content-sdk-component-data-strategy/SKILL.md · 29 lines

What it actually says

Component data strategy (Angular)

Detail: AGENTS-loaders-and-di.md#how-data-reaches-components Read first: src/app/pages/page.component.ts, src/app/shared/layout.component.ts

When

Deciding how a component gets its Sitecore data
Data is present on SSR but missing after a client-side navigation

Rules

Mapped components receive fields / params / rendering from <sc-placeholder> — do not fetch inside them
Page-level data comes from route resolve data (route.data['page'], ['dictionary']), read with toSignal() as in PageComponent
For reactive access anywhere in the tree, inject SitecoreContextService (page(), dictionary(), isEditing, effectiveLocale)
New page-level data means a new loader, not a component-level fetch
Loader results must be JSON-serializable — they cross TransferState on first paint and POST /_data on navigation

Stop

Stop if introducing a second data-fetch path (component-level HttpClient for layout data) without clear need

Docs: Content SDK for Angular.

Changes

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 · 29 lines · 27 tokens per session scan A dc411c723b09

Subscribe to this mod's changes

content-sdk-component-data-strategy is a skill published in the GitHub repository Sitecore/content-sdk (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 327 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-10-02.

Backend and APIs Frontend

mem0-oss-to-platform

Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…

mem0ai/mem0 · 217 tokens

agui-dotnet-protobuf

Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…

ag-ui-protocol/ag-ui · 162 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

fastapi-router-py

Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.

microsoft/skills · 46 tokens

dev-runtime

How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…

langwatch/langwatch · 172 tokens

migrate-segw-to-rap

Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…

arc-mcp/arc-1 · 106 tokens