Umbraco-CMS-MCP-Dev: Command for Claude Code

.claude/commands/upgrade-umbraco.md

upgrade-umbraco is a command for Claude Code from umbraco/Umbraco-CMS-MCP-Dev. It costs 0 tokens per session (2,857 once invoked), scanned C, original, MIT.

A command for upgrading the demo Umbraco site's packages to a newer released version and regenerating its API client. Umbraco is a content management system, and an API client is code that lets the project communicate with its API.

In plain words
What is it for?
Use it to upgrade to the latest stable or a specific Umbraco version, test the change in an isolated setup, regenerate API code, and review upgrade-related impact.
Why use it?
It helps reveal which tools, tests, schemas, and endpoints may be affected by an Umbraco upgrade. It also surfaces newly available endpoints that could support future tools.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths.

This is umbraco/Umbraco-CMS-MCP-Dev's own configuration. It tells Claude Code how to work on Umbraco-CMS-MCP-Dev itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Umbraco-CMS-MCP-Dev configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash scripts/bootstrap-demo-site.sh --force.

Reuse

Borrowing it

Nothing to install: this file belongs to umbraco/Umbraco-CMS-MCP-Dev. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/umbraco/Umbraco-CMS-MCP-Dev/main/.claude/commands/upgrade-umbraco.md
Clone the repo
git clone --depth 1 https://github.com/umbraco/Umbraco-CMS-MCP-Dev

Made for: Claude Code.

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 upgrade-umbraco

README.md
[![agentmods](https://agentmods.dev/badge/commands/umbraco/umbraco-cms-mcp-dev/upgrade-umbraco/github.svg)](https://agentmods.dev/commands/umbraco/umbraco-cms-mcp-dev/upgrade-umbraco)
Your own site
<a href="https://agentmods.dev/commands/umbraco/umbraco-cms-mcp-dev/upgrade-umbraco"><img src="https://agentmods.dev/badge/commands/umbraco/umbraco-cms-mcp-dev/upgrade-umbraco/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 upgrade-umbraco

Your own site · 80×15
<a href="https://agentmods.dev/commands/umbraco/umbraco-cms-mcp-dev/upgrade-umbraco"><img src="https://agentmods.dev/badge/commands/umbraco/umbraco-cms-mcp-dev/upgrade-umbraco.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,857 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.00000 $0.02857
Opus 5 $0.00000 $0.01429
Sonnet 5 $0.00000 $0.00571
Haiku 4.5 $0.00000 $0.00286

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

Security

Grade C, and why

upgrade-umbraco scanned grade C with 2 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 5d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

bash scripts/bootstrap-demo-site.sh --force # rm -rf demo-site/ and recopy the upgraded template

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `dotnet`, `npm`, `curl`, `python3` on PATH
.claude/commands/upgrade-umbraco.md · 190 lines

How it starts

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

/upgrade-umbraco

Upgrade the demo-site Umbraco packages to the latest released version, regenerate the API client, identify schema/endpoint impact on tools and tests, and surface new endpoints for tool creation.

Usage

/upgrade-umbraco                   # upgrade to latest stable
/upgrade-umbraco 17.4.0            # upgrade to a specific version

ARGUMENTS: $ARGUMENTS

Prerequisites

  • Local SQL Server reachable from demo-site/appsettings.local.json
  • A working .env with UMBRACO_CLIENT_ID, UMBRACO_CLIENT_SECRET, UMBRACO_BASE_URL
  • dotnet, npm, curl, python3 on PATH
  • Use a new, empty database for each upgrade — do not reuse the previous version's DB. The Development config has InstallUnattended: true (admin [email protected] / 1234567890), so a brand-new DB auto-installs on first boot, and scripts/create-api-user.mjs then creates both the API user and the umbraco-back-office-mcp OAuth client. Nothing needs to be carried over from the old DB.

Steps

1. Set up an isolated worktree

Use the superpowers:using-git-worktrees skill to create .worktrees/upgrade-umbraco-<version> on a chore/upgrade-umbraco-<version> branch. Run npm install and npm run compile to confirm a clean baseline before changing anything.

2. Identify the target version

If no argument is given, query NuGet for the latest non-prerelease:

curl -s "https://api.nuget.org/v3-flatcontainer/umbraco.cms/index.json" \
  | python3 -c "import json,sys; d=json.load(sys.stdin); \
      print(next(v for v in reversed(d['versions']) \
      if not any(x in v for x in ['rc','beta','alpha','pre'])))"

Also confirm the matching version of Umbraco.Cms.DevelopmentMode.Backoffice. Umbraco.ExaminePDF is on its own track — check for an updated major if the CMS major changed.

3. Update package versions in the template

Edit demo-site-template/demo-site-template.csproj:

<PackageReference Include="Umbraco.Cms" Version="X.Y.Z" />
<PackageReference Include="Umbraco.Cms.DevelopmentMode.Backoffice" Version="X.Y.Z" />

Read the full file on GitHub · 190 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. 5d ago Changed · +7 lines 4a85adcad897
  2. 9d ago First seen · 183 lines · 0 tokens per session scan C 4def615ee79f

Subscribe to this mod's changes

upgrade-umbraco is a command published in the GitHub repository umbraco/Umbraco-CMS-MCP-Dev (39 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,857 tokens. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.