What is kirby-content-migration?

A tool for planning and applying bulk changes to content in Kirby, a content management system. It supports changes such as renaming fields, moving values, transforming content, and updating files across languages.

Use it to update Kirby fields, blocks, page content, languages, drafts, or file metadata in controlled batches.

It reduces the risk of changing many pages incorrectly by requiring a planned scope, validation, previewed differences, and confirmation before writing.

kirby-content-migration — Skill for Claude Code and Codex by bnomei

Install

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.

Any agent

npx skills add bnomei/kirby-mcp --skill kirby-content-migration

Clone the repo

git clone --depth 1 https://github.com/bnomei/kirby-mcp

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bnomei/kirby-mcp/kirby-content-migration/github.svg)](https://agentmods.dev/skills/bnomei/kirby-mcp/kirby-content-migration)

Your own site

<a href="https://agentmods.dev/skills/bnomei/kirby-mcp/kirby-content-migration"><img src="https://agentmods.dev/badge/skills/bnomei/kirby-mcp/kirby-content-migration/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bnomei/kirby-mcp/kirby-content-migration"><img src="https://agentmods.dev/badge/skills/bnomei/kirby-mcp/kirby-content-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 717 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00049	$0.00717
Opus 5	$0.00024	$0.00358
Sonnet 5	$0.00010	$0.00143
Haiku 4.5	$0.00005	$0.00072

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

Security

Grade A, and why

kirby-content-migration 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 12d 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.

skills/kirby-content-migration/SKILL.md · 73 lines

How it starts

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

Kirby Content Migration

Quick start

Follow the workflow below for safe, confirm-first migrations.

KB entry points

kirby://kb/scenarios/16-batch-update-content
kirby://kb/scenarios/74-update-blocks-programmatically
kirby://kb/scenarios/34-content-file-cleanup-script
kirby://kb/scenarios/75-update-file-metadata

Required inputs

Source and target fields plus transform rules.
Scope (templates/ids/sections) and batch size.
Language and draft handling rules.
Exclusions or derived fields that must not change.

Plan template

List source field, target field, transform rule, and a before/after example.
Specify scope (templates/ids), languages, and draft handling.
Note exclusions (derived fields, computed values, or generated files).

Plan-validate-execute

Write a changes.json plan with explicit page ids/uuids and new values.
Validate the plan against blueprint and field schemas, plus a sample diff.
Apply in batches (confirm=false preview, then confirm=true).

Verification checklist

Preview diffs for each field type before writing.
Confirm language scope and batch boundaries.
Re-render representative pages after apply.

Common pitfalls

Writing updates before reading field update schemas.
Migrating large batches without confirm previews.

Workflow

Ask for exact transformations, scope (pages/templates/sections), languages, draft handling, and any derived fields that must not be written.
Call kirby:kirby_init, then ensure runtime availability with kirby:kirby_runtime_status and kirby:kirby_runtime_install if needed.
Identify target pages:
- Prefer explicit page ids/uuids from the user.
- Otherwise derive a list using kirby://roots and the content directory structure.
Search the KB with kirby:kirby_search for related playbooks (examples: "batch update content", "update blocks programmatically", "content file cleanup script", "update file metadata").
Read field storage rules before writing:
- kirby://fields/update-schema
- kirby://field/{type}/update-schema for each involved field type.
Read a small sample with kirby:kirby_read_page_content (or kirby://page/content/{encodedIdOrUuid}) and produce a diff-style preview.
Use kirby://tool-examples for safe, copy-ready kirby:kirby_update_page_content payloads.

Read the full file on GitHub · 73 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.

12d ago First seen · 73 lines · 49 tokens per session scan A 9e324eb72e66

Subscribe to this mod's changes

kirby-content-migration is a skill published in the GitHub repository bnomei/kirby-mcp (59 stars, last pushed 12d ago), licensed MIT. It adds 49 tokens to every session and 717 once invoked, about $0.0002 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-30.

Backend and APIs Claude Code Databases agentic-workflow cli codex-cli commands google-gemini

supabase-setup

Use this skill when setting up or changing a Supabase database - schema, migrations, row-level security, seeds, typed clients, or connecting an app to a hosted project. Covers the safe order of operations and the checks that prevent a public table or an unreviewable schema change.

chadixearth/graphyloop · 62 tokens

prisma-patterns

Prisma ORM patterns for TypeScript backends â€” schema design, query optimization, transactions, pagination, and critical traps like updateMany returning count not records, $transaction timeouts, migrate dev resetting the DB, @updatedAt skipped on bulk writes, and serverless connection exhaustion.