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 skills add LibreChat-AI/librechat.ai --skill librechat-docsgit clone --depth 1 https://github.com/LibreChat-AI/librechat.aiWrote 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/skills/librechat-ai/librechat.ai/librechat-docs)<a href="https://agentmods.dev/skills/librechat-ai/librechat.ai/librechat-docs"><img src="https://agentmods.dev/badge/skills/librechat-ai/librechat.ai/librechat-docs/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/skills/librechat-ai/librechat.ai/librechat-docs"><img src="https://agentmods.dev/badge/skills/librechat-ai/librechat.ai/librechat-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 23 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00024 | $0.00301 |
| Opus 5.5 | $0.00010 | $0.00120 |
| Sonnet 5.5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
librechat-docs 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.
What it actually says
LibreChat Documentation
Use LibreChat's official documentation as the source of truth for installation, configuration, features, administration, and troubleshooting.
Documentation workflow
- Fetch
https://www.librechat.ai/llms.txtto find the most relevant documentation page. - Fetch a page as Markdown by appending
.mdto its canonical docs URL. For example, usehttps://www.librechat.ai/docs/configuration/librechat_yaml.mdfor the custom configuration reference. - Use
https://www.librechat.ai/llms-full.txtonly when the question spans multiple sections or the curated index is insufficient. - Cite the canonical HTML documentation URL in the final answer so the user can read the rendered page.
- Check the changelog when behavior may differ between LibreChat releases.
Accuracy and safety
- Do not invent configuration keys, environment variables, commands, defaults, or supported integrations.
- Preserve the exact spelling and casing of settings shown in the documentation.
- Distinguish settings in
.env,librechat.yaml, Docker Compose overrides, and provider dashboards. - Use placeholders for credentials and secrets. Never ask users to publish secret values.
- If the documentation does not answer the question, say so and direct the user to the LibreChat GitHub discussions or issue tracker.
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 First seen · 25 lines · 24 tokens per session scan A bffd53838ea9
librechat-docs is a skill published in the GitHub repository LibreChat-AI/librechat.ai (662 stars, last pushed 28d ago), licensed MIT. It adds 24 tokens to every session and 301 once invoked, about $0.0001 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 skills, from other repositories
wiki_submit
Submit wiki documentation pages to Wegent backend API. Simplifies the HTTP POST process for wiki content submission.
skill-creator
A guide for creating or improving an agent skill: a SKILL.md file that gives an AI a repeatable workflow for a specific task. It covers the skill’s name, search keywords, instructions, failure handling, and examples where needed.
github
A writing guide for GitHub issues, pull requests, code reviews, and release notes in Zhin projects. GitHub is a service where teams track bugs, discuss changes, review code, and publish project updates.
documentation-authoring
Create structured docs from scratch — PRDs, technical specs, design docs, decision records, knowledge bases. Use when drafting documentation, writing proposals, defining requirements, or planning features.
documentation-patterns
Templates and structural patterns for API docs, feature docs, config guides, and REST endpoint documentation. Use when structuring docs, applying Markdown templates, or standardizing doc formats.
documentation-quality
Documentation quality standards and writing principles. Use when establishing formatting rules, reviewing doc quality metrics, creating writing guidelines, or enforcing consistent documentation style across a project.