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/leanzero-srl/leanzero-mcp-doc-processor/claude-mdgit clone --depth 1 https://github.com/leanzero-srl/leanzero-mcp-doc-processorWhat 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.12227 | $0.12227 |
| Opus 5 | $0.06114 | $0.06114 |
| Sonnet 5 | $0.02445 | $0.02445 |
| Haiku 4.5 | $0.01223 | $0.01223 |
Grade A, and why
leanzero-mcp-doc-processor 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 2d 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 — 676 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 on code in this repository.
CRITICAL WARNING: MANDATORY REITERATION PROTOCOL
READ THIS FIRST: Before proceeding with ANY task, you MUST follow the Context-First Protocol.
The Most Important Rule in This Document:
Every single interaction MUST begin with reiterating your understanding of the task. There are NO exceptions.
- You cannot ask questions first
- You cannot proceed to planning first
- You cannot start implementation first
- You MUST reiterate your understanding first
Simple Formula for Success:
Task Received → Read Context → Reiterate Understanding → Wait for Confirmation → Proceed
Do NOT skip the reiteration step. Ever.
PRIMARY DIRECTIVE: CONTEXT-FIRST PROTOCOL
This is your most important rule and overrides all others. Before any other action, you MUST follow this protocol.
Phase 1: Gather Project Context (MANDATORY FIRST STEP)
Upon receiving a task, immediately gather context by:
-
Read Project Documentation (priority order):
CLAUDE.md- This file, understanding project structure, MCP protocol rules, and conventionssrc/index.js- MCP server entry point, tool definitions and dispatch (~450 lines)- The specific tool handler file(s) relevant to the task in
src/tools/ - Any service or utility files referenced by the tool handlers
- Any files specifically mentioned by the human agent
-
Analyze the Request:
- Identify the core requirement
- Map the request to existing project files or patterns
- Determine what information is available vs. unclear
- Identify which MCP tools and which internal modules are affected
Phase 2: Reiterate Understanding and Confirm (MANDATORY - NO EXCEPTIONS)
CRITICAL: This phase is REQUIRED for EVERY task.
There are NO exceptions to this rule:
- Even if the task seems simple
- Even if you think you understand perfectly
- Even if the human provided detailed instructions
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.
- 2d ago First seen · 676 lines · 12,227 tokens per session scan A c7b636d493c3
leanzero-mcp-doc-processor CLAUDE.md is an instructions file published in the GitHub repository leanzero-srl/leanzero-mcp-doc-processor (1 stars, last pushed 27d ago), licensed MIT. It adds 12,227 tokens to every session, about $0.0611 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.