LibreChat is an open-source, self-hosted chat application that lets people use AI models and agent tools through one interface. It supports individuals and teams who want features such as model switching, file-based code work, searches, actions, and multi-user access. The catalogue entries extend LibreChat with skills and instructions for its workflows.
Borrowing it
Nothing to install: this file belongs to danny-avila/LibreChat. 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/danny-avila/LibreChat/main/CLAUDE.mdgit clone --depth 1 https://github.com/danny-avila/LibreChatWrote 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/danny-avila/librechat/claude-md)<a href="https://agentmods.dev/instructions/danny-avila/librechat/claude-md"><img src="https://agentmods.dev/badge/instructions/danny-avila/librechat/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/danny-avila/librechat/claude-md"><img src="https://agentmods.dev/badge/instructions/danny-avila/librechat/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.05135 | $0.05135 |
| Opus 5.5 | $0.02054 | $0.02054 |
| Sonnet 5.5 | $0.01027 | $0.01027 |
| Haiku 4.5 | $0.00513 | $0.00513 |
Grade A, and why
LibreChat 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 1mo 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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LibreChat
Project Overview
LibreChat is a monorepo with the following key workspaces:
| Workspace | Language | Side | Dependency | Purpose |
|---|---|---|---|---|
/api |
JS (legacy) | Backend | packages/api, packages/data-schemas, packages/data-provider, @librechat/agents |
Express server — minimize changes here |
/packages/api |
TypeScript | Backend | packages/data-schemas, packages/data-provider |
New backend code lives here (TS only, consumed by /api) |
/packages/data-schemas |
TypeScript | Backend | packages/data-provider |
Database models/schemas, shareable across backend projects |
/packages/data-provider |
TypeScript | Shared | — | Shared API types, endpoints, data-service — used by both frontend and backend |
/client |
TypeScript/React | Frontend | packages/data-provider, packages/client |
Frontend SPA |
/packages/client |
TypeScript | Frontend | packages/data-provider |
Shared frontend utilities |
The source code for @librechat/agents (major backend dependency, same team) lives at
https://github.com/danny-avila/agents.
Workspace Boundaries
- All new backend code must be TypeScript in
/packages/api. /apiholds wiring, not behavior. When a change would add logic to a CJS file under/api— a branch, a helper, a validation step, a new service call — that logic goes in/packages/api, and the JS file keeps only what wires it up: requires, route registration, request plumbing, and the call into the TS module.api/server/services/MCPRequestContext.jsis the shape, at thirteen lines of re-export. "Minimum" describes how much behavior/apigains, not how small the diff is: lifting a function into/packages/apiand calling it is the larger diff and the correct one. Editing an existing CJS file is the common case and the rule applies there, not only to new files.- Database-specific shared logic goes in
/packages/data-schemas. - Frontend/backend shared API logic (endpoints, types, data-service) goes in
/packages/data-provider. - Build data-provider from project root:
npm run build:data-provider. - Database contracts stay inside
/packages/data-schemas. A Mongoose type in an exported signature —FilterQuery,Types.ObjectId,Document,HydratedDocument— makes the storage engine part of that module's public API, and every consumer then depends on Mongo instead of on the data it needs. Take and return plain typed objects, and express the query behind a data-schemas method. The boundary already leaks across dozens of files in/packages/api, so the rule is to stop widening it rather than to rewrite what exists;/clientcarries none of it and must stay that way. - New levers ship configurable. A limit, timeout, toggle or capability introduced in code earns
a field on
configSchema(packages/data-provider/src/config.ts) so an operator can set it inlibrechat.yaml, with a default that reproduces today's behavior. Hard-coded constants and env-only switches need a reason. The schema is also what keeps one definition of the value instead of a constant, a fallback and a doc line that drift apart. - A backend module takes its dependencies, it does not reach for them. Code in
/packages/apishould receive its config, database methods and clients from the caller the waycreateModels(mongoose)receives the app's connection, rather than importing app singletons or reading global state. A module the caller constructs can be tested without a running app and moved to another workspace without a rewrite; one that callsgetInstance()can do neither. This is the backend half of "Client State Ownership" — pass it in, do not reach for it. The static singletons underpackages/api/src/mcpare the shape to stop extending, not a pattern to copy. - Integrations arrive through an interface the caller supplies. A provider SDK, storage backend, vector store or OAuth server is injected, so a second implementation is a new argument instead of a new branch in shared code, and a test can exercise the real logic against a substitute at the boundary rather than mocking the module that holds it.
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.
- 1mo ago Changed · +96 lines · +1,643 tokens per session 4585a29ce9a0
- 1mo ago Changed · +57 lines · +906 tokens per session 1a9bcb03e742
- 1mo ago First seen · 224 lines · 2,586 tokens per session scan A cb13ba3b7314
LibreChat CLAUDE.md is an instructions file published in the GitHub repository danny-avila/LibreChat (46,271 stars, last pushed 2d ago), licensed MIT. It adds 5,135 tokens to every session, about $0.0205 per session on Opus 5.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-30.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.