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

.claude/commands/migrate-tests.md

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

A command that changes MCP tool tests from an older response-reading style to a newer shared style using test helpers. MCP is a standard way for AI assistants to call tools.

In plain words
What is it for?
Use it on a test folder when migrating tests that parse response text to helpers for structured data, errors, and snapshots.
Why use it?
It removes repeated manual code for reading test responses and brings tests into the project's standard format. This can make tests easier to update consistently.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

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 reads a path above its own folder, which exists only inside the repository. The line is import { createOutputSchema } from "../post/create-entity.js";.

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/migrate-tests.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 migrate-tests

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/umbraco/umbraco-cms-mcp-dev/migrate-tests"><img src="https://agentmods.dev/badge/commands/umbraco/umbraco-cms-mcp-dev/migrate-tests.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,457 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.00000 $0.02457
Opus 5.5 $0.00000 $0.00983
Sonnet 5.5 $0.00000 $0.00491
Haiku 4.5 $0.00000 $0.00246

Measured 2mo ago against content hash 37136763a7e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

migrate-tests 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 2mo 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.

.claude/commands/migrate-tests.md · 339 lines

How it starts

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

/migrate-tests

Migrates MCP tool tests from the old pattern to the new standardized pattern using test helpers.

Usage

/migrate-tests <test-folder-path>

Example:

/migrate-tests src/umbraco-api/tools/document-type/__tests__

Description

This command helps migrate MCP tool tests from the old pattern (JSON.parse with getResultText) to the new standardized pattern using validateStructuredContent, validateErrorResult, and createSnapshotResult.

Old vs New Patterns

Accessing Response Data

Old Pattern:

import { createMockRequestHandlerExtra, getResultText } from "@/test-helpers/create-mock-request-handler-extra.js";

const result = await Tool.handler(params, createMockRequestHandlerExtra());
const data = JSON.parse(getResultText(result));
expect(data.name).toBe("expected");

New Pattern:

import { createMockRequestHandlerExtra, validateStructuredContent } from "@/test-helpers/create-mock-request-handler-extra.js";
import { getEntityResponse } from "@/umbraco-api/umbracoManagementAPI.zod.js";

const result = await Tool.handler(params, createMockRequestHandlerExtra());
const data = validateStructuredContent(result, getEntityResponse);
expect(data.name).toBe("expected");

Validating Error Results

Old Pattern:

const result = await Tool.handler(params, createMockRequestHandlerExtra());
expect(result.isError).toBe(true);
// or check content[0].text for error message

New Pattern:

import { validateErrorResult } from "@/test-helpers/create-mock-request-handler-extra.js";

const result = await Tool.handler(params, createMockRequestHandlerExtra());
validateErrorResult(result);
expect(result).toMatchSnapshot();

Snapshot Testing

Old Pattern:

// Manual normalization of content[0].text
const normalizedResult = {
  ...result,
  content: result.content.map(content => {
    const parsed = JSON.parse((content as any).text);
    return {
      ...content,
      text: JSON.stringify({
        ...parsed,
        items: normalizeIds(parsed.items)
      })
    };
  })
};
expect(normalizedResult).toMatchSnapshot();

Read the full file on GitHub · 339 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. 2mo ago First seen · 339 lines · 0 tokens per session scan A 37136763a7e2

Subscribe to this mod's changes

migrate-tests is a command published in the GitHub repository umbraco/Umbraco-CMS-MCP-Dev (39 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,457 tokens. 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.