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-plugin-developmentgit 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-plugin-development)<a href="https://agentmods.dev/skills/bnomei/kirby-mcp/kirby-plugin-development"><img src="https://agentmods.dev/badge/skills/bnomei/kirby-mcp/kirby-plugin-development/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-plugin-development"><img src="https://agentmods.dev/badge/skills/bnomei/kirby-mcp/kirby-plugin-development.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.00037 | $0.00752 |
| Opus 5.5 | $0.00015 | $0.00301 |
| Sonnet 5.5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
kirby-plugin-development 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 9d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kirby Plugin Development
Use Kirby 6 conventions for new work. For existing Panel plugins, consult kirby://kb/panel/compat-k5-k6-migration before porting code.
Kirby 6 plugin contracts
- Register PHP field classes, not arrays. Use
DisplayFieldfor former custom sections,InputFieldfor input andValueFieldfor value-only fields. Built-in sections auto-convert; custom sections do not. - Build Panel code for Vue 3 with kirbyup 4 / Node.js 24+. Import Vue from
vue, preservevalue/input, declare emits and never bundle a second Vue runtime. - Bundle compatible kirbyuse if needed, leaving Vue external; see
kirby://kb/panel/tooling-kirbyusefor loader details. - Use trusted-HTML APIs only with escaped/sanitized input. Use Panel instance APIs and route controller
action/factory()contracts; preserve valid closures. - Auth methods/challenges are instance classes under
Kirby\Auth; pending login is not authenticated. Hash challenge secrets and test recovery/denied paths.
KB entry points
kirby://kb/scenarios/84-kirby-6-core-contractskirby://kb/panel/reference-runtimekirby://kb/scenarios/04-share-templates-controllers-via-pluginkirby://kb/scenarios/05-kirbytext-kirbytags-hookskirby://kb/scenarios/15-custom-blocks-nested-blockskirby://kb/scenarios/17-extend-kirbytagskirby://kb/scenarios/59-monolithic-plugin-setupkirby://kb/scenarios/60-plugin-workflow-local-testing
Required inputs
- Plugin id (vendor/name) and scope.
- Extension points (hooks/value or display fields/tags/blocks/areas).
- Distribution plan (project-only or composer package).
Minimal plugin skeleton
Kirby::plugin('vendor/name', [
'hooks' => [],
'blueprints' => [],
'snippets' => [],
]);
Local testing
- Use the local workflow guide to test without publishing.
- Render affected pages and verify plugin registration.
Common pitfalls
- Using inconsistent plugin ids or folder names.
- Registering hooks that assume Panel or API is always enabled.
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.
- 9d ago Changed · +12 lines b7ba1970f2c6
- 1mo ago First seen · 54 lines · 37 tokens per session scan A 87c7dc25b47d
kirby-plugin-development is a skill published in the GitHub repository bnomei/kirby-mcp (67 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 752 once invoked, about $0.0001 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
// nodemailer import nodemailer from 'nodemailer'.
supabase
Skill "supabase" from dhaupin/vant, covering supabase, when to use, what to do, 1. connect and supabase-js.
test-integration
Test how components work together. Test database + API, auth + user service, etc. Use when testing multi-component flows or after unit tests pass.
api
Application programming interface.
environment
APIKEY=secret123 DATABASEURL=postgres://localhost DEBUG=true.
graphql
Skill "graphql" from dhaupin/vant, covering graphql, when to use, what to do, 1. query and 2. mutation.