Borrowing it
Nothing to install: this file belongs to Antonytm/mcp-sitecore-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Antonytm/mcp-sitecore-server/main/AGENTS.mdgit clone --depth 1 https://github.com/Antonytm/mcp-sitecore-serverWrote 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/instructions/antonytm/mcp-sitecore-server/agents-md)<a href="https://agentmods.dev/instructions/antonytm/mcp-sitecore-server/agents-md"><img src="https://agentmods.dev/badge/instructions/antonytm/mcp-sitecore-server/agents-md.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.1 | $0.03206 | $0.03206 |
| Opus 5 | $0.01603 | $0.01603 |
| Sonnet 5 | $0.00641 | $0.00641 |
| Haiku 4.5 | $0.00321 | $0.00321 |
Grade A, and why
mcp-sitecore-server AGENTS.md 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcp-sitecore-server
An MCP server (@antonytm/mcp-sitecore-server) that gives agents read/write access to
Sitecore over four independent API surfaces: the Authoring and Management GraphQL
API, the Item Service (REST/SSC), GraphQL Edge/preview, and Sitecore PowerShell
Extensions (SPE) remoting. It targets both SitecoreAI and XM/XP, so treat every surface as
optional and let the gating decide — see tool gating below.
Tests
package.json holds the scripts. Two things it does not say:
npm run test:unitneeds no Sitecore instance and should always pass.npm testbuilds, bundles and runs the full suite, which needs a CM in.envwith SPE Remoting enabled — but no seeded content: every live file creates what it needs and deletes it again (tests/fixtures.ts).- The
--config vitest.unit.config.tsflag scopes totests/unit; both configs map the@/alias, so the unit files collect under either.
npx vitest run --config vitest.unit.config.ts tests/unit/projection.test.ts
npx vitest run --config vitest.unit.config.ts -t "name of the case"
Writing a live test: call seedScratch(label, [names]) at the top of the file and
register afterAll(() => scratch.cleanup()). That creates /sitecore/content/MCP-<label>-<unique>
and a matching template, and the cleanup takes both, plus anything the test archived on its
way through. The other fixtures cover what a family needs on top: seedPresentation /
applyPresentation for layouts and renderings, seedUser / seedRole for accounts,
assignWorkflow / addWorkflowEvent for workflow state, ensureLanguage for a second
language (a different locale per file — files run in parallel, and a shared language is
deleted out from under the file still using it), plus seedTemplate, seedChild and
linkItems.
Assert against the seed, not against a constant: scratch.template.name, never
"Sample Item". The two things a new live test gets wrong most often are that the tools
return the projected shape (ID, not ID.ToString; nine fields on an account, not the
whole User graph — see projection.ts), and that SPE reports a missing item as an error
result rather than an empty one, so check isError instead of parsing.
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 · 201 lines · 3,206 tokens per session scan A 4e8e74f42a29
mcp-sitecore-server AGENTS.md is an instructions file published in the GitHub repository Antonytm/mcp-sitecore-server (52 stars, last pushed 5d ago), licensed Apache-2.0. It adds 3,206 tokens to every session, about $0.0160 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-09-03.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.