Borrowing it
Nothing to install: this file belongs to sandervanscheepen/silverstripe-mcp. 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/sandervanscheepen/silverstripe-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/sandervanscheepen/silverstripe-mcpWrote 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/sandervanscheepen/silverstripe-mcp/claude-md)<a href="https://agentmods.dev/instructions/sandervanscheepen/silverstripe-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/sandervanscheepen/silverstripe-mcp/claude-md/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/instructions/sandervanscheepen/silverstripe-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/sandervanscheepen/silverstripe-mcp/claude-md.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.00384 | $0.00384 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
silverstripe-mcp CLAUDE.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 10d 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
Silverstripe MCP Server - Agent Instructions
This is a Model Context Protocol (MCP) server that validates AI-generated PHP code for Silverstripe 6 compatibility.
For full development details, see CONTRIBUTING.md.
Key Rules
- Always run
ss-validatoron any generated Silverstripe PHP code before presenting to the user. Keep calling until no issues remain. - This project requires PHP 8.3+ and Node.js 18+.
- The PHP analyzer uses nikic/php-parser for AST analysis. Validators are plugins in
php/src/Plugins/. - Configuration mappings live in
php/src/Config/(namespace mappings, removed methods, hook renames, elemental mappings).
Quick Commands
# Install dependencies
npm install
cd php && composer install && cd ..
# Build TypeScript
npm run build
# Run all tests
npm run test:all
# Test PHP analyzer directly
cd php && php bin/analyze '{"code": "<?php use SilverStripe\\ORM\\ArrayList;"}'
What the Validators Detect
- Wrong namespace imports (SS5 → SS6 class renames)
- Outdated BuildTask patterns (
run(HTTPRequest)→execute(InputInterface, PolyOutput)) - Deprecated
FormField::Value()usage (split intodataValue(),presentedValue(),processedValue()) - Removed methods (
Controller::has_curr(),Requirements::themedCSS(), etc.) - Extension hook visibility issues (public → protected)
- Deprecated
Config::inst()->get()pattern - Elemental module namespace changes (auto-enabled when Elemental imports detected)
The list-sections and get-documentation tools are available in the MCP server for looking up SS6 changelog details.
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.
- 10d ago First seen · 42 lines · 384 tokens per session scan A d6ee9ce14ae6
silverstripe-mcp CLAUDE.md is an instructions file published in the GitHub repository sandervanscheepen/silverstripe-mcp (5 stars, last pushed 6mo ago), licensed MIT. It adds 384 tokens to every session, about $0.0019 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 instructions, from other repositories
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.
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).
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.
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).
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.