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.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.03492 | $0.03492 |
| Opus 5 | $0.01746 | $0.01746 |
| Sonnet 5 | $0.00698 | $0.00698 |
| Haiku 4.5 | $0.00349 | $0.00349 |
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 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 — 281 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. - Keep
/apichanges to the absolute minimum (thin JS wrappers calling into/packages/api). - 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.
Branching and Pull Requests
- Branch off
dev, and targetdevwith every pull request. All work lands ondevfirst. mainis the released branch. It is kept as a fast-forward ofdevand synced as-is, so it is always an ancestor ofdev— equal to it right after a sync, behind it otherwise. It never carries a commit thatdevdoes not have.- Never open a backport pull request to
main. Anything merged todevreachesmainat the next sync; a second pull request for the same change is redundant. - The repository's default branch is
main, sogh pr createand the GitHub UI target it unless told otherwise — always pass--base devexplicitly. - Pull requests opened against
mainare retargeted todevautomatically by.github/workflows/pr-retarget-dev.yml. Thetarget: mainlabel exempts one, as do release-bound upstream branches (dev,release/*,hotfix/*). Backport branches are deliberately not exempt — a backport merged straight tomainis what breaks the fast-forward invariant. Fixes #Ndoes not close the issue. GitHub honors closing keywords only when a pull request merges into the default branch (main). Merging todevdoes not close anything, and the later fast-forward ofmainis not a merge event either — close linked issues by hand.- Git worktrees share one stash stack.
refs/stashlives in the common.gitdirectory, so a baregit stash popin one worktree can take work stashed in another. Prefer a throwaway WIP commit; if you must stash,git stash push -m <tag>andapplythat specific entry.
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 Changed · +57 lines · +906 tokens per session 1a9bcb03e742
- 7d 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 (42,847 stars, last pushed today), licensed MIT. It adds 3,492 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-30.
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.