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 skills add smithdak/claude-marketplace --skill sitecore-classicgit clone --depth 1 https://github.com/smithdak/claude-marketplaceWrote 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/skills/smithdak/claude-marketplace/sitecore-classic)<a href="https://agentmods.dev/skills/smithdak/claude-marketplace/sitecore-classic"><img src="https://agentmods.dev/badge/skills/smithdak/claude-marketplace/sitecore-classic/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/skills/smithdak/claude-marketplace/sitecore-classic"><img src="https://agentmods.dev/badge/skills/smithdak/claude-marketplace/sitecore-classic.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.00028 | $0.03083 |
| Opus 5 | $0.00014 | $0.01541 |
| Sonnet 5 | $0.00006 | $0.00617 |
| Haiku 4.5 | $0.00003 | $0.00308 |
Grade A, and why
sitecore-classic 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 11d 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 — 530 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bundled Skills
This plugin includes the following additional skills for comprehensive development context:
| Skill | Purpose |
|---|---|
frontend-classic |
CSS/SASS organization, JavaScript/jQuery patterns, BEM naming |
frontend-razor |
Razor view syntax, layouts, partials, tag helpers |
backend-csharp |
C#/.NET DI patterns, service architecture, async/await |
fullstack-classic |
jQuery AJAX integration, form handling, anti-forgery tokens |
These skills are automatically included when you install the Sitecore Classic Analyzer plugin.
Sitecore 10.x Development Patterns
Helix Architecture
Layer Responsibilities
Foundation Layer
- Cross-cutting concerns shared across features
- Examples: Logging, Serialization, DI registration, Indexing, ORM
- No business logic, only technical infrastructure
- Can reference other Foundation modules
Feature Layer
- Business capabilities and features
- Examples: Navigation, Search, Forms, Checkout, Articles
- Each feature is independent and self-contained
- Can reference Foundation modules only
- NEVER reference other Feature modules
Project Layer
- Tenant/site-specific implementations
- Examples: Website, Corporate, MobileApp
- Assembles features for specific sites
- Can reference Feature and Foundation modules
Dependency Rule
Project → Feature → Foundation
Features must NEVER reference other Features. If shared logic is needed, extract to Foundation.
Folder Structure
src/
├── Foundation/
│ └── {Module}/
│ ├── code/
│ │ ├── DependencyInjection/
│ │ ├── Services/
│ │ └── Foundation.{Module}.csproj
│ └── serialization/
│ └── {Module}.module.json
├── Feature/
│ └── {Module}/
│ ├── code/
│ │ ├── Controllers/
│ │ ├── Models/
│ │ ├── Services/
│ │ ├── Repositories/
│ │ └── Feature.{Module}.csproj
│ └── serialization/
│ ├── Templates/
│ ├── Renderings/
│ └── {Module}.module.json
└── Project/
└── {Site}/
├── code/
│ ├── Layouts/
│ └── Project.{Site}.csproj
└── serialization/
├── Content/
└── {Site}.module.json
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.
- 11d ago First seen · 530 lines · 28 tokens per session scan A bfbe09647d6f
sitecore-classic is a skill published in the GitHub repository smithdak/claude-marketplace (3 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 3,083 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
with-tanstack-query
Compose Angular Query with signal-owned Table filtering, sorting, and pagination state using reactive query options, manual row-model boundaries, direct query data, server counts, and valid injection context.
auth-web-cloudbase
CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.
service-digital-engagement-channel-configure
Configures and deploys enhanced chat Messaging Channels for Messaging for In-App and Web (MIAW). Use when the user needs to create, deploy, and activate a messaging channel configured with Omni-Channel Flow, Omni-Channel Queue, User, or Agentforce Service Agent routing. Generates MessagingChannel metadata, deploys it…
om-system-extension
Extend installed Open Mercato modules through UMES enrichers, interceptors, mutation guards, widgets, menus, entity extensions, events, component/page replacements, and overrides. Use for "extend core", "add field/column/action", "hide page", "intercept API", "UMES", or "rozszerz moduł".