Borrowing it
Nothing to install: this file belongs to ozonejunkieau/esp32-docs-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/ozonejunkieau/esp32-docs-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/ozonejunkieau/esp32-docs-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/ozonejunkieau/esp32-docs-mcp/claude-md)<a href="https://agentmods.dev/instructions/ozonejunkieau/esp32-docs-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ozonejunkieau/esp32-docs-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/ozonejunkieau/esp32-docs-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ozonejunkieau/esp32-docs-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.03501 | $0.03501 |
| Opus 5 | $0.01750 | $0.01750 |
| Sonnet 5 | $0.00700 | $0.00700 |
| Haiku 4.5 | $0.00350 | $0.00350 |
Grade A, and why
esp32-docs-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 8d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — operating guide
An MCP server exposing semantic search over ESP32 documentation: the ESP-IDF guides and API reference, and the per-chip Technical Reference Manuals. Chunks are embedded locally with MLX and stored in LanceDB.
Python 3.12+, uv only — never pip or uv pip. Flat module layout, no src/.
This file is what you need to work here safely. The reasoning behind the design lives elsewhere, and is worth reading before changing anything structural:
| Read | For |
|---|---|
| docs/architecture.md | Why the pipelines are shaped this way; what was tried and deleted |
| docs/trm-latex.md | The TRM LaTeX ingest — read before touching latex_parser.py |
| docs/building-the-corpus.md | Running a build or a refresh |
| docs/development.md | The justfile, the tests, the fixtures |
| docs/usage.md | Querying the server and reading results |
| README.md | The public description |
Hard rules
Never chunk ESP-IDF .rst sources. The documentation is a build, not a set
of files: constants are substituted from soc_caps/Kconfig at build time,
only:: branches are selected per target, and the entire API reference is
doxygen output that does not exist in the source tree. Consume the XML builder's
output — not the .doctrees pickles, which are written before only:: is
evaluated. Rationale and the deleted .rst attempt:
architecture.md.
That rule does not transfer to the TRM. Its build-time dependencies are
shallow and compiling would yield PDFs — less structure, not more. Parsing the
LaTeX source is correct there. \ifglobal is build scaffolding, but \iftagged
does gate content in 48 files and must be evaluated rather than flattened.
See trm-latex.md so it
does not get "fixed" back.
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.
- 8d ago First seen · 238 lines · 3,501 tokens per session scan A a015afc11ce9
esp32-docs-mcp CLAUDE.md is an instructions file published in the GitHub repository ozonejunkieau/esp32-docs-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 3,501 tokens to every session, about $0.0175 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.