agentmods.dev

upgrades

upgrades is a skill for Claude Code from bethanychamberlain/claude-skills-librechat. It costs 50 tokens per session (1,299 once invoked), scanned A, original, MIT.

A set of instructions for upgrading LibreChat, a self-hosted chat application, between versions or moving its data and settings.

In plain words
What is it for?
Use it to plan or carry out LibreChat upgrades, migrate data, handle changed agent permissions, and recover from upgrade problems.
Why use it?
It helps identify breaking changes, required database migrations, deprecated settings, and deployment risks before an upgrade.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: positional $N argument.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the librechat-ops plugin — 4 skills shipped together

not rated 3repo 5mo ago A scan 50 tokens original MIT

Good fit Use it to plan or carry out LibreChat upgrades, migrate data, handle changed agent permissions, and recover from upgrade problems.

Compare 6 skills from other repositories ↓
View source ↗ bethanychamberlain/claude-skills-librechat
Install

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.

Claude Code
/plugin marketplace add bethanychamberlain/claude-skills-librechat
Claude Code
/plugin install librechat-ops

Made for: Claude Code.

Or install librechat-ops, the plugin that ships this one along with the rest of its 4 skills.

Wrote 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.

agentmods badge for upgrades

README.md
[![agentmods](https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/upgrades/github.svg)](https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/upgrades)
Your own site
<a href="https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/upgrades"><img src="https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/upgrades/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.

agentmods 80×15 button for upgrades

Your own site · 80×15
<a href="https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/upgrades"><img src="https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/upgrades.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,299 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01299
Opus 5 $0.00025 $0.00649
Sonnet 5 $0.00010 $0.00260
Haiku 4.5 $0.00005 $0.00130

Measured 10d ago against content hash 8cf460d28153, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

upgrades 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.

librechat-ops/skills/upgrades/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

LibreChat Upgrades

You are an expert in LibreChat version management. Your goal is to help users safely upgrade LibreChat, handle breaking changes, and recover from upgrade 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:

  1. What LibreChat version are you currently running?
  2. What version do you want to upgrade to?
  3. How is it deployed? (Docker local / Docker remote / Kubernetes)
  4. Do you have a recent backup?

How This Skill Works

Mode 1: Plan an Upgrade

When the user wants to understand what an upgrade involves before doing it.

  1. Load ${CLAUDE_PLUGIN_ROOT}/references/breaking-changes.md to check for breaking changes between their current and target version
  2. Load ${CLAUDE_PLUGIN_ROOT}/references/upgrade-procedure.md for the standard checklist
  3. Identify any .env variable changes, deprecated settings, or required migrations
  4. Produce a step-by-step plan with risks highlighted

Mode 2: Execute an Upgrade

When the user is ready to perform the upgrade.

  1. Verify they have a backup (if not, walk them through creating one)
  2. Load ${CLAUDE_PLUGIN_ROOT}/references/upgrade-procedure.md
  3. Walk through each step: stop, backup, pull, check for breaking changes, start, verify
  4. After restart, show verification commands

Mode 3: Fix Post-Upgrade Issues

When something broke after an upgrade.

  1. Check what version they upgraded from and to
  2. Load ${CLAUDE_PLUGIN_ROOT}/references/breaking-changes.md to find relevant changes
  3. Check logs: docker compose logs api
  4. Common fixes: clear old images, update .env vars, rebuild
  5. If the issue is config-related, suggest the config skill (librechat-core)

Which mode to use:

  • User says "plan", "what changed", "should I upgrade", "what's new" -> Mode 1
  • User says "upgrade now", "update", "pull latest" -> Mode 2
  • User says "broke after upgrade", "error after update", "rollback" -> Mode 3

Read the full file on GitHub · 125 lines

Changes

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.

  1. 10d ago First seen · 125 lines · 50 tokens per session scan A 8cf460d28153

Subscribe to this mod's changes

upgrades is a skill published in the GitHub repository bethanychamberlain/claude-skills-librechat (3 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 1,299 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.

Claude CodeDatabasesDevOps and cloudagent-skillsagentic-aianthropic-claudeclaude-aiclaude-code-plugins
Related

Other skills, from other repositories

TEMPLATE

../../../agents/personas/TEMPLATE.md.

alirezarezvani/claude-skills · 0 tokens

dev-supabase

Backend development with Supabase. Trigger when the user wants to configure auth, the database, or Supabase storage.

christopherlouet/claude-base · 28 tokens

dev-prisma

Development with Prisma ORM (schema, migrations, type-safe queries, Accelerate, transactions). Trigger when the user wants to add a model, create a migration, optimize Prisma queries, or when schema.prisma is detected in the project.

christopherlouet/claude-base · 51 tokens

ops-database

Database schema design. Trigger when the user wants to create tables, migrations, or optimize queries.

christopherlouet/claude-base · 23 tokens

mysql-checkpointing

Make n8n workflows idempotent, resumable, and safe at scale using MySQL/Postgres checkpoint tables, batch processing patterns, duplicate prevention, and dynamic table creation. Use this skill whenever the user is building an n8n workflow that processes batches of data, handles webhooks, polls APIs, or runs on a…

masteranime/n8n-claude-skills · 137 tokens

sql-code-review

Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimisation prompt for…

MarieLynneBlock/arcanum-artifex · 65 tokens