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 skills add bnomei/kirby-mcp --skill kirby-content-migrationgit clone --depth 1 https://github.com/bnomei/kirby-mcpWrote 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/skills/bnomei/kirby-mcp/kirby-content-migration)<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.
<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>- NVIDIA SkillSpector pass
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.00989 |
| Opus 5.5 | $0.00020 | $0.00396 |
| Sonnet 5.5 | $0.00010 | $0.00198 |
| Haiku 4.5 | $0.00005 | $0.00099 |
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 11d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kirby Content Migration
Use Kirby 6 conventions for new work. For CMS upgrades, read kirby://kb/scenarios/83-migrate-kirby-5-to-6 before planning content writes.
Schema safety
- Inspect normalized model fields, not only raw
kirby_blueprint_readconfiguration.hasValue: falseexcludes display fields;nullmeans unresolved, not writable. - Never write
pagelist,filelist,info,statsorbuttonsvalues. Picker selections usepagepicker,filepicker,userpicker; read their canonical update-schema guides. - Renaming a legacy picker type does not rename its stored key. Resolve existing targets; a new random UUID is not a relationship target.
- Audit Symfony YAML changes in nested content: quote dates/reserved scalars and use real booleans. Invalid options now survive saves; transform removed keys explicitly.
- Only follow actual update-schema links or entries in
kirby://fields/update-schema; do not invent guides for arbitrary/display types. - PHP updates can accept supported objects/collections; MCP arguments still require JSON storage payloads. Check serialization, empty-number behavior and validation in
kirby://kb/scenarios/84-kirby-6-core-contractsbefore bulk writes.
Quick start
- Follow the workflow below for safe, confirm-first migrations.
KB entry points
kirby://kb/scenarios/16-batch-update-contentkirby://kb/scenarios/74-update-blocks-programmaticallykirby://kb/scenarios/34-content-file-cleanup-scriptkirby://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
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.
- 11d ago Changed · +11 lines f82b5fc6a45e
- 1mo ago First seen · 73 lines · 49 tokens per session scan A 9e324eb72e66
kirby-content-migration is a skill published in the GitHub repository bnomei/kirby-mcp (67 stars, last pushed 7d ago), licensed MIT. It adds 49 tokens to every session and 989 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
supabase
Skill "supabase" from dhaupin/vant, covering supabase, when to use, what to do, 1. connect and supabase-js.
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.
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.
ship-safe-scan
Quick scan for leaked secrets — API keys, passwords, tokens, database URLs. Use when the user wants to check for hardcoded secrets or exposed credentials.
firebase
Use when building on Firebase — Firestore data modeling, Security Rules, Auth and custom claims, Cloud Functions, Storage, modular Web/Admin SDK imports — including symptoms like a database open to the internet, a query rejected by rules, or a doc stuck at 1 write/sec. NOT managed-Postgres BaaS with SQL and RLS (that…
notion-connector
Use when wiring server code or a cron job to Notion as an ops backend over its HTTP API: pushing or mirroring database rows, two-way sync without duplicates, page blocks, or an integration broken by the 2025-09-03 data-source split. NOT generic REST wiring (that is api-connector-builder), NOT inbound Notion webhook…