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 instructions/aself101/mcp-secure-server/claude-mdgit clone --depth 1 https://github.com/aself101/mcp-secure-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/aself101/mcp-secure-server/claude-md)<a href="https://agentmods.dev/instructions/aself101/mcp-secure-server/claude-md"><img src="https://agentmods.dev/badge/instructions/aself101/mcp-secure-server/claude-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 | $0.00888 | $0.00888 |
| Opus 5 | $0.00444 | $0.00444 |
| Sonnet 5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
mcp-secure-server 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 4d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
MCP Security Framework - a secure-by-default MCP server built on the official SDK with 5-layer validation. Provides defense-in-depth against traditional attacks and AI-driven threats.
Commands
# Run all tests
npm test
# Run specific test suites
npm run test:unit
npm run test:integration
npm run test:performance
npm run test:coverage
# Watch mode for development
npm run test:watch
# Start test server (for Claude Desktop integration)
npm run minimal-server
Run a single test file:
npx vitest run test/unit/utils/canonical.test.js
Architecture
Security Layer System
The framework uses a 5-layer validation pipeline:
Request → Layer 1 (Structure) → Layer 2 (Content) → Layer 3 (Behavior) → Layer 4 (Semantics) → Layer 5 (Contextual) → MCP Server
- Layer 1 - Structure (
layer1-structure.js): JSON-RPC format validation, request size limits, encoding validation - Layer 2 - Content (
layer2-content.js): Pattern detection for path traversal, command injection, SQL injection, XSS, buffer overflow, CRLF injection - Layer 3 - Behavior (
layer3-behavior.js): Rate limiting, burst detection, request pattern analysis - Layer 4 - Semantics (
layer4-semantics.js): Tool contract enforcement, resource access policies, quota management - Layer 5 - Contextual (
layer5-contextual.js): Custom validators, domain restrictions, OAuth validation, response filtering
Key Components
ValidationPipeline(src/security/utils/validation-pipeline.js): Orchestrates sequential layer executionSecureMcpServer(src/security/mcp-secure-server.js): Unified secure server with 5-layer validationContextualValidationLayer(src/security/layers/layer5-contextual.js): Extensible Layer 5 for custom validators- Attack patterns defined in
src/security/layers/layer-utils/content/dangerous-patterns.js
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.
- 4d ago First seen · 103 lines · 888 tokens per session scan A 644f24d85fe3
mcp-secure-server CLAUDE.md is an instructions file published in the GitHub repository aself101/mcp-secure-server (2 stars, last pushed 10d ago), licensed MIT. It adds 888 tokens to every session, about $0.0044 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.