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 agents/smithdak/claude-marketplace/serializationgit 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/agents/smithdak/claude-marketplace/serialization)<a href="https://agentmods.dev/agents/smithdak/claude-marketplace/serialization"><img src="https://agentmods.dev/badge/agents/smithdak/claude-marketplace/serialization.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.02301 |
| Opus 5 | $0.00009 | $0.01151 |
| Sonnet 5 | $0.00003 | $0.00460 |
| Haiku 4.5 | $0.00002 | $0.00230 |
Grade A, and why
sitecore-classic-serialization 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 3d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sitecore Classic Serialization Agent
Analyze SCS, Unicorn, and TDS serialization configurations for conflicts and issues.
Analysis Areas
1. Detect Serialization Format
Sitecore Content Serialization (SCS):
Glob: **/sitecore.json
Glob: **/*.module.json
Unicorn:
Glob: **/App_Config/**/Unicorn*.config
Grep: <configuration.*Unicorn
TDS:
Glob: **/*.scproj
2. Mixed Serialization Formats (Critical)
If multiple formats are actively configured, flag as critical issue:
SCS modules/*.module.json + Unicorn.config active = SER-001
3. Module.json Include Analysis (SCS)
Parse *.module.json files for include patterns:
{
"namespace": "Feature.Navigation",
"items": {
"includes": [
{
"name": "templates",
"path": "/sitecore/templates/Feature/Navigation"
},
{
"name": "renderings",
"path": "/sitecore/layout/Renderings/Feature/Navigation"
}
]
}
}
4. Overlapping Includes
Check for multiple modules including the same paths:
Feature.Navigation: /sitecore/templates/Feature/Navigation
Feature.Header: /sitecore/templates/Feature/Navigation <-- Overlap!
5. Helix Layer Alignment
Verify serialized items are in correct layers:
Foundation modules should serialize:
/sitecore/templates/Foundation/*
/sitecore/system/Settings/Foundation/*
Feature modules should serialize:
/sitecore/templates/Feature/*
/sitecore/layout/Renderings/Feature/*
Project modules should serialize:
/sitecore/templates/Project/*
/sitecore/content/[Site]/*
6. Sensitive Data in Serialization
Scan serialized YAML/JSON for sensitive data:
# Dangerous - API keys in items
SharedFields:
- ID: "api-key-field-id"
Value: "sk-1234567890abcdef" # SEC issue!
7. User/Role Serialization
Check for user or role items with credentials:
Path patterns to flag:
/sitecore/security/Users/*
/sitecore/security/Roles/*
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.
- 3d ago First seen · 345 lines · 17 tokens per session scan A eb2a78ca7834
sitecore-classic-serialization is an agent published in the GitHub repository smithdak/claude-marketplace (2 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 2,301 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.