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 instantcms-dev/instantcms-mcp --skill instantcms-migrationgit clone --depth 1 https://github.com/instantcms-dev/instantcms-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/instantcms-dev/instantcms-mcp/instantcms-migration)<a href="https://agentmods.dev/skills/instantcms-dev/instantcms-mcp/instantcms-migration"><img src="https://agentmods.dev/badge/skills/instantcms-dev/instantcms-mcp/instantcms-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/instantcms-dev/instantcms-mcp/instantcms-migration"><img src="https://agentmods.dev/badge/skills/instantcms-dev/instantcms-mcp/instantcms-migration.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00027 | $0.00132 |
| Opus 5.5 | $0.00011 | $0.00053 |
| Sonnet 5.5 | $0.00005 | $0.00026 |
| Haiku 4.5 | $0.00003 | $0.00013 |
Grade A, and why
instantcms-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 1mo 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.
What it actually says
InstantCMS migration
Inspect the current schema and target version before proposing SQL. Use introspect_database, describe_table, and scaffold_migration; do not invent core table columns.
Keep install, upgrade, and rollback behavior distinct. Preserve existing data, make repeated execution predictable where possible, and flag destructive changes before applying them.
Validate the complete addon with audit_instantcms_project and verify install/uninstall on the target InstantCMS version before calling the migration ready.
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.
- 1mo ago First seen · 13 lines · 27 tokens per session scan A 67d94f29f3e8
instantcms-migration is a skill published in the GitHub repository instantcms-dev/instantcms-mcp (11 stars, last pushed 9d ago), licensed MIT. It adds 27 tokens to every session and 132 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-31.
Other skills, from other repositories
payload
Use when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
data-governance
Use this skill when designing or reviewing data governance: schema ownership, PII handling, retention, lineage, access policy, and migration safety for services and data stores. Triggers: user says "data governance", "PII", "schema ownership", "retention policy", "data lineage", "migration safety".
backup-recovery
Design and verify backups and restoration for owned databases, files and application state. Use when preparing recovery, migrating data or testing backups; protect the source and prove restore into an isolated destination before calling recovery ready.
database-development
Implement database access, models and queries with explicit consistency, transactions and bounded results. Use when working with SQL, document databases, Redis or ORM clients; use database-migrations for schema rollout/recovery and verify actual engine/client compatibility.
database-migrations
Design and verify schema migrations, bounded backfills and deployment compatibility for databases. Use when adding constraints or indexes, changing column types, evolving schemas or recovering failed migrations; distinguish reversible application rollback from data restoration.
webiny-api-opensearch-catalog
Name: createOpenSearchClient Import: import { createOpenSearchClient } from "webiny/api/opensearch" Source: @webiny/api-opensearch/client.ts.