Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/umbraco/umbraco-cms-mcp-dev/migrate-toolsgit clone --depth 1 https://github.com/umbraco/Umbraco-CMS-MCP-DevWrote 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/commands/umbraco/umbraco-cms-mcp-dev/migrate-tools)<a href="https://agentmods.dev/commands/umbraco/umbraco-cms-mcp-dev/migrate-tools"><img src="https://agentmods.dev/badge/commands/umbraco/umbraco-cms-mcp-dev/migrate-tools.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.03123 |
| Opus 5 | $0.00000 | $0.01562 |
| Sonnet 5 | $0.00000 | $0.00625 |
| Haiku 4.5 | $0.00000 | $0.00312 |
Grade A, and why
migrate-tools 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 4d 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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/migrate-tools
Migrates MCP tools from the old pattern to the new standardized pattern using helper functions.
Usage
/migrate-tools <tool-group-path>
Example:
/migrate-tools src/umbraco-api/tools/document-type
Description
This command helps migrate MCP tools from the old manual pattern (direct client calls with JSON.stringify) to the new standardized pattern using helper functions like executeGetApiCall, executeVoidApiCall, and createToolResult.
Old vs New Patterns
DELETE Operations (Void)
Old Pattern:
import { UmbracoManagementClient } from "@umb-management-client";
import { CreateUmbracoTool } from "@/helpers/create-umbraco-tool.js";
const DeleteTool = CreateUmbracoTool(
"delete-item",
"Deletes an item",
schema.shape,
async ({ id }) => {
const client = UmbracoManagementClient.getClient();
await client.deleteById(id);
return {
content: [{ type: "text" as const, text: JSON.stringify({ success: true }) }],
};
}
);
New Pattern:
import { ToolDefinition } from "types/tool-definition.js";
import { withStandardDecorators, executeVoidApiCall, CAPTURE_RAW_HTTP_RESPONSE } from "@/helpers/mcp/tool-decorators.js";
const DeleteTool = {
name: "delete-item",
description: "Deletes an item",
inputSchema: schema.shape,
annotations: {
destructiveHint: true,
},
slices: ['delete'],
handler: (async ({ id }: { id: string }) => {
return executeVoidApiCall((client) =>
client.deleteById(id, CAPTURE_RAW_HTTP_RESPONSE)
);
}),
} satisfies ToolDefinition<typeof schema.shape>;
export default withStandardDecorators(DeleteTool);
GET Operations (Returns Data)
Old Pattern:
const GetTool = CreateUmbracoTool(
"get-item",
"Gets an item",
schema.shape,
async ({ id }) => {
const client = UmbracoManagementClient.getClient();
const response = await client.getById(id);
return {
content: [{ type: "text" as const, text: JSON.stringify(response) }],
};
}
);
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.
- 4d ago First seen · 396 lines · 0 tokens per session scan A 7afd638847a2
migrate-tools is a command published in the GitHub repository umbraco/Umbraco-CMS-MCP-Dev (39 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,123 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.