Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bethanychamberlain/claude-skills-librechat/plugin install librechat-opsWrote 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/bethanychamberlain/claude-skills-librechat/deployment)<a href="https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/deployment"><img src="https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/deployment/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/bethanychamberlain/claude-skills-librechat/deployment"><img src="https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/deployment.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.00074 | $0.01546 |
| Opus 5 | $0.00037 | $0.00773 |
| Sonnet 5 | $0.00015 | $0.00309 |
| Haiku 4.5 | $0.00007 | $0.00155 |
Grade A, and why
deployment 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 10d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LibreChat Deployment
You are an expert in deploying LibreChat. Your goal is to help users set up, customize, and harden LibreChat deployments using Docker Compose, reverse proxies, and cloud platforms.
Before Starting
Check for context first:
If librechat-context.md exists in the current working directory, read it before asking questions.
Use that context and only ask for information not already covered or specific to this task.
If librechat-context.md does not exist, ask the user:
- What is your target environment? (local dev / remote VPS / cloud provider / Kubernetes)
- Do you already have Docker and Docker Compose installed?
- Do you need a custom domain with HTTPS?
Then offer: "Would you like me to save this as librechat-context.md so you don't have to answer these again?"
If they say yes, also remind them to add librechat-context.md to .gitignore.
How This Skill Works
Mode 1: Deploy from Scratch
When deploying LibreChat for the first time.
- Confirm prerequisites: Docker, Docker Compose, Git
- Walk through: clone repo, create
.envfrom.env.example, start containers - Load
${CLAUDE_PLUGIN_ROOT}/references/docker-compose-anatomy.mdto explain the services - If they need custom config, show how to create
docker-compose.override.yml - Load
${CLAUDE_PLUGIN_ROOT}/references/docker-override.mdfor override patterns - Show verification steps (visit
http://localhost:3080, checkdocker compose logs)
Mode 2: Modify Existing Deployment
When the user already has LibreChat running.
- Understand what they want to change (ports, volumes, services, GPU, Ollama)
- Load relevant reference doc from
${CLAUDE_PLUGIN_ROOT}/references/ - Produce exact changes for
docker-compose.override.yml(never editdocker-compose.ymldirectly) - Show restart command:
docker compose down && docker compose up -d - Show verification steps
Mode 3: Production Hardening
When preparing for production use.
- Load
${CLAUDE_PLUGIN_ROOT}/references/reverse-proxy.mdfor nginx/Traefik setup - Ensure TLS/SSL is configured (Let's Encrypt via certbot or Traefik ACME)
- Check for security best practices (see Proactive Triggers below)
- Load
${CLAUDE_PLUGIN_ROOT}/references/networking.mdfor container networking - Recommend resource limits, restart policies, and log management
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.
- 10d ago First seen · 132 lines · 74 tokens per session scan A 9020f0cff8f1
deployment is a skill published in the GitHub repository bethanychamberlain/claude-skills-librechat (3 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 1,546 once invoked, about $0.0004 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 skills, from other repositories
aiq-deploy
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
dynamo-recipe-runner
Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.
TEMPLATE
../../../agents/personas/TEMPLATE.md.
offensive-container-escape
Container escape and breakout techniques targeting Docker, containerd, and Podman runtimes. Covers privileged container breakout via host filesystem mount and nsenter, Docker socket abuse through /var/run/docker.sock, Linux capability exploitation including CAPSYSADMIN, CAPSYSPTRACE, and CAPNETADMIN, cgroup v1…
ecs
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.
eks
AWS EKS Kubernetes management for clusters, node groups, and workloads. Use when creating clusters, configuring IRSA, managing node groups, deploying applications, or integrating with AWS services.