agentmods.dev

kirby-upgrade-and-maintenance

kirby-upgrade-and-maintenance is a skill for Claude Code, Codex from bnomei/kirby-mcp. It costs 40 tokens per session (528 once invoked), scanned A, original, MIT.

Kirby maintenance tools for upgrading the CMS and its dependencies, including checking plugins, reviewing Composer changes, and testing representative pages. Composer is the dependency manager used by many PHP projects.

In plain words
What is it for?
Use them to plan Kirby version upgrades, audit dependencies, check plugin compatibility, run smoke tests, and stage changes across sites or environments.
Why use it?
They reduce upgrade failures caused by breaking changes, incompatible plugins, or untested custom code, and define how to roll back safely.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 59repo 13d ago A scan SkillSpector: pass 40 tokens original MIT

Good fit Use them to plan Kirby version upgrades, audit dependencies, check plugin compatibility, run smoke tests, and stage changes across sites or environments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bnomei/kirby-mcp/kirby-upgrade-and-maintenance
View source ↗ bnomei/kirby-mcp forum.getkirby.com
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-upgrade-and-maintenance
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.

agentmods badge for kirby-upgrade-and-maintenance

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/bnomei/kirby-mcp/kirby-upgrade-and-maintenance"><img src="https://agentmods.dev/badge/skills/bnomei/kirby-mcp/kirby-upgrade-and-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 528 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00528
Opus 5 $0.00020 $0.00264
Sonnet 5 $0.00008 $0.00106
Haiku 4.5 $0.00004 $0.00053

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

Security

Grade A, and why

kirby-upgrade-and-maintenance 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 13d 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-upgrade-and-maintenance/SKILL.md · 65 lines

How it starts

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

Kirby Upgrade and Maintenance

Quick start

  • Follow the workflow below for safe, incremental upgrades.

KB entry points

  • kirby://kb/panel/compat-k5-k6-migration
  • kirby://kb/panel/tooling-kirbyup
  • kirby://kb/glossary/kirbyup
  • kirby://kb/glossary/plugin

Required inputs

  • Current and target Kirby versions.
  • Environment constraints and downtime tolerance.
  • Plugin compatibility risks and rollback expectations.

Default upgrade checklist

  • Read the target version guide and note breaking changes.
  • Update composer.json constraints, then review the lockfile diff.
  • Run project scripts and render representative pages.
  • Verify runtime commands and CLI version match.

Rollback note

  • Keep a copy of the previous composer.lock and vendor/ state.

Rollback checklist

  • Restore the previous composer.lock.
  • Reinstall dependencies and re-run smoke tests.
  • Re-render representative pages to confirm behavior.

Staged upgrade pattern

  • Upgrade a single environment/site first, then roll out to others.
  • Validate plugins and custom code before multi-site rollout.

Common pitfalls

  • Skipping plugin compatibility checks.
  • Upgrading multiple major versions in one jump.

Workflow

  1. Call kirby:kirby_init or gather baseline data with kirby:kirby_info and kirby:kirby_composer_audit.
  2. Inventory plugins for compatibility risks: kirby:kirby_plugins_index.
  3. Use kirby:kirby_online to find official upgrade guides and breaking changes for the target version (prefer kirby:kirby_search first).
  4. Build a project-specific checklist of required code/config changes.
  5. Ask for confirmation before dependency updates that change the lockfile.
  6. Verify:
    • run project scripts discovered in the composer audit
    • call kirby:kirby_cli_version to confirm the installed version
    • ensure runtime commands are in sync: kirby:kirby_runtime_status and kirby:kirby_runtime_install if needed
    • render representative pages with kirby:kirby_render_page(noCache=true)
  7. Summarize changes, remaining risks, and a short manual QA checklist.

Read the full file on GitHub · 65 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. 13d ago First seen · 65 lines · 40 tokens per session scan A 9c1c6e388a7e

Subscribe to this mod's changes

kirby-upgrade-and-maintenance is a skill published in the GitHub repository bnomei/kirby-mcp (59 stars, last pushed 13d ago), licensed MIT. It adds 40 tokens to every session and 528 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 APIsClaude CodeDevOps and cloudagentic-workflowclicodex-clicommandsgoogle-gemini
Related

Other skills, from other repositories

defending-applications

Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…

telagod/code-abyss · 152 tokens

designing-architectures

Architecture knowledge reference covering API design, security architecture, cloud-native patterns, caching strategies, message queues, and data security. Use when designing system architecture, APIs, or cloud-native infrastructure.

telagod/code-abyss · 43 tokens

backend

Backend engineering judgment, distilled from a stronger model - invoke when CHOOSING a tech stack, language, database, queue, or architecture; designing a service, API, business logic, or schema; making a system production-ready (observability, failure handling, security); or reviewing server-side code and judging…

telagod/code-abyss · 99 tokens

api-contract-design

Use this skill when freezing the interface between a backend and its clients before parallel work starts, or when changing an endpoint other code already calls - request/response shapes, status codes, error envelope, pagination, filtering, idempotency, versioning, and the breaking-change rules. Covers writing the…

chadixearth/graphyloop · 79 tokens

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

yolo-detector

Use when designing or verifying Ultralytics YOLO detection, segmentation, tracking, or pose inference with licensed models and stable JSON outputs.

Hipson47/Hipson · 32 tokens