Borrowing it
Nothing to install: this file belongs to mrlesmithjr/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/mrlesmithjr/mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/mrlesmithjr/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/mrlesmithjr/mcp/claude-md)<a href="https://agentmods.dev/instructions/mrlesmithjr/mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/mrlesmithjr/mcp/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.1 | $0.04813 | $0.04813 |
| Opus 5 | $0.02406 | $0.02406 |
| Sonnet 5 | $0.00963 | $0.00963 |
| Haiku 4.5 | $0.00481 | $0.00481 |
Grade A, and why
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 6d 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code when working in the mcp uv workspace.
Status: ACTIVE Last Updated: 2026-07-20
What this repo is
A uv workspace that consolidates all personal MCP servers into a single lockfile,
shared dev tooling, and a marketplace generator. Each tool lives under packages/
as a subtree-merged member.
Structure
mcp/
├── pyproject.toml # Virtual workspace root (no distribution)
├── uv.lock # Single root lockfile (authoritative)
├── .claude-plugin/
│ └── marketplace.json # GENERATED -- do not hand-edit
├── .agents/plugins/
│ └── marketplace.json # GENERATED Codex marketplace -- do not hand-edit
├── packages/
│ ├── mcp-common/ # Shared library (mrlesmithjr-mcp-common); PyPI-ready
│ ├── weather-tools/ # mrlesmithjr-mcp-weather-tools
│ │ ├── .claude-plugin/
│ │ │ └── plugin.json # GENERATED: Claude plugin metadata (no hooks field)
│ │ ├── .codex-plugin/
│ │ │ └── plugin.json # GENERATED: Codex plugin metadata
│ │ ├── .mcp.json # GENERATED: Claude Code MCP definition (runs hooks/run_server.sh)
│ │ └── hooks/
│ │ ├── hooks.json # GENERATED: SessionStart hook wiring
│ │ ├── install_deps.sh # GENERATED: SessionStart venv installer
│ │ └── run_server.sh # GENERATED: cold-start launcher
│ ├── ynab-tools/ # mrlesmithjr-mcp-ynab-tools (same layout)
│ │ # ships NO launchagents/: the dashboard is opt-in
│ │ # via `ynab dashboard install` (see below)
│ ├── homeops/, lawnops/ # launchagents/: plist templates (__HOME__) + ops
│ │ # scripts, shipped in the plugin and auto-loaded
│ ├── contacts-tools/ # mrlesmithjr-mcp-contacts-tools (Google People API; ContactsManager/PyObjC retained but unwired)
│ └── ... # 14 packages total; the 13 plugins share this layout
├── scripts/
│ ├── gen_marketplace.py # Reads packages/*/pyproject.toml, emits per-package files
│ └── install_launchagents.sh # Manual/dev re-install of all LaunchAgents from the checkout
└── dev/
└── register_dev.py # Registers <tool>-dev servers pointing at .venv/bin/
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.
- 6d ago First seen · 359 lines · 4,813 tokens per session scan A dded971513c2
mcp CLAUDE.md is an instructions file published in the GitHub repository mrlesmithjr/mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 4,813 tokens to every session, about $0.0241 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).
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.
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.