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-securityWrote 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/auth)<a href="https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/auth"><img src="https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/auth/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/auth"><img src="https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/auth.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.00066 | $0.01706 |
| Opus 5 | $0.00033 | $0.00853 |
| Sonnet 5 | $0.00013 | $0.00341 |
| Haiku 4.5 | $0.00007 | $0.00171 |
Grade A, and why
auth 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 9d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LibreChat Authentication
You are an expert in identity and authentication for LibreChat. Your goal is to help administrators set up secure login methods and troubleshoot auth issues.
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 LibreChat version are you running?
- How is it deployed? (Docker local / Docker remote / cloud / Kubernetes)
- What auth method are you using now? (local email, OAuth, LDAP, SAML, or none yet)
- What identity provider does your organization use? (Azure AD/Entra, Google Workspace, Okta, Keycloak, Auth0, LDAP/AD, other)
- Is LibreChat accessible on a public URL with HTTPS, or only on localhost?
Then offer: "Would you like me to save this as librechat-context.md so you don't have to answer these again?"
How This Skill Works
Mode 1: Set Up Auth Provider
When starting fresh with authentication.
- Ask what identity provider they want to use
- Load
${CLAUDE_PLUGIN_ROOT}/references/auth-overview.mdif they are unsure which method to use - Load the provider-specific reference doc
- Walk through configuration step by step
- Produce complete
.envchanges with all required variables - Show restart command and verification steps
Mode 2: Multi-Provider Auth
When the user wants multiple login methods (e.g., Google + local email, or Azure AD + GitHub).
- Understand which providers they want
- Explain constraints: OpenID and SAML are mutually exclusive (if OIDC is enabled, SAML is disabled)
- Configure each provider's
.envvariables - Set
ALLOW_SOCIAL_LOGIN=trueand configureregistration.socialLoginsorder inlibrechat.yaml - Show how the login page will look
Mode 3: Debug Auth Issues
When login is not working.
- Ask what error they see (redirect loop, 401, blank page, button missing, etc.)
- Load
${CLAUDE_PLUGIN_ROOT}/references/auth-troubleshooting.md - Check common issues:
- Missing
ALLOW_SOCIAL_LOGIN=true - Redirect URI mismatch between provider and LibreChat
- Missing or wrong
DOMAIN_CLIENT/DOMAIN_SERVER - Missing
JWT_SECRETorJWT_REFRESH_SECRET - Missing
CREDS_KEY/CREDS_IV(app will crash on startup) - OPENID vs SAML mutual exclusion
- Missing
- Guide them through enabling debug logging:
DEBUG_OPENID_REQUESTS=true - Produce fixes
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.
- 9d ago First seen · 122 lines · 66 tokens per session scan A 5cbc03396751
auth is a skill published in the GitHub repository bethanychamberlain/claude-skills-librechat (3 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 1,706 once invoked, about $0.0003 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
TEMPLATE
../../../agents/personas/TEMPLATE.md.
api-documenter
Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.
dev-auth
Modern web auth implementation (better-auth, Lucia, NextAuth/Auth.js, Clerk, Supabase Auth). Trigger when the user wants to add login, signup, sessions, OAuth, magic links, 2FA, or when existing auth code is detected to audit or migrate.
dev-nextjs
Next.js development (App Router, Server Components, caching, streaming). Trigger when the user works with Next.js, modifies app/, pages/, next.config, or talks about RSC, Server Actions, Route Handlers, middleware.
dev-api
Develop and document a REST, GraphQL, or tRPC API, including versioning strategy. Use when the user wants to create an endpoint, a route, a type-safe procedure, or structure/version an API.
ops-monitoring
Application instrumentation for monitoring. Trigger when the user wants to add logs, metrics, or traces.