Ghost is a publishing platform for creating websites, blogs, memberships, subscriptions, and newsletters. Publishers and developers can use it through managed hosting or run it themselves, while contributors work on its monorepo, themes, and API.
Borrowing it
Nothing to install: this file belongs to TryGhost/Ghost. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TryGhost/Ghost/main/.agents/skills/create-database-migration/SKILL.mdgit clone --depth 1 https://github.com/TryGhost/GhostWrote 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/tryghost/ghost/create-database-migration)<a href="https://agentmods.dev/skills/tryghost/ghost/create-database-migration"><img src="https://agentmods.dev/badge/skills/tryghost/ghost/create-database-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/tryghost/ghost/create-database-migration"><img src="https://agentmods.dev/badge/skills/tryghost/ghost/create-database-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.00145 | $0.00783 |
| Opus 5.5 | $0.00058 | $0.00313 |
| Sonnet 5.5 | $0.00029 | $0.00157 |
| Haiku 4.5 | $0.00015 | $0.00078 |
Grade A, and why
Create database 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 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Database Migration
Read the canonical human guidance in
docs/practices/database-migrations.md
before making a migration. This skill is the executable checklist that
accompanies it.
Instructions
If you are adding a new table whose shape is still changing, consider marking it as in development instead of writing a migration yet; see "New tables still in development" in the guide.
- Create a new, empty migration file:
pnpm gx generate migration <kebab-case-slug>from the repository root. IMPORTANT: do not create the migration file manually; always use this script to create the initial empty migration file. The slug must be kebab-case (e.g.add-column-to-posts). - The above command will create a new directory in
ghost/core/server/data/migrations/versionsif needed, create the empty migration file with the appropriate name, and bump the core and admin package versions to RC if this is the first migration after a release. - Update the migration file with the changes you want to make in the database, following the existing patterns in the codebase. Where appropriate, prefer to use the utility functions in
ghost/core/server/data/migrations/utils/*. - Update the schema definition file in
ghost/core/server/data/schema/schema.js, and make sure it aligns with the latest changes from the migration. - Test the migration manually from the repository root:
pnpm knex-migrator migrate --v {version directory} --force - Roll the migration back to test
down():pnpm knex-migrator rollback --v {previous version} --force, then migrate forward again. - Run the migration integration test, which covers initialization, rollback, forward migration, and idempotency:
cd ghost && pnpm test:single test/integration/migrations/migration.test.js. It needs MySQL running, whichpnpm devstarts. - If adding or dropping a table, update
ghost/core/server/data/exporter/table-lists.jsas appropriate. The consistency assertion inghost/test/unit/server/data/exporter/index.test.jschecks that every schema table is classified in the exporter lists. - Run the focused exporter unit test when the table lists change:
cd ghost && pnpm test:single test/unit/server/data/exporter/index.test.js. - For schema changes, run the schema-sync test:
cd ghost && pnpm test:single test/integration/migrations/schema-sync.test.ts. For changes to fixtures, default settings, or default routes, run the database integrity test and update only the affected hash:cd ghost && pnpm test:single test/unit/server/data/schema/integrity.test.ts - Run unit tests in Ghost core, and iterate until they pass:
cd ghost && pnpm test:unit
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 d820282319af
- 16d ago Changed 6cc8f379698c
- 18d ago Changed 1634134ab3f7
- 19d ago Changed 6180dfe3045b
- 20d ago Changed · -1 tokens per session ef27152d9c94
- 1mo ago Changed · +4 lines 230caca5db58
- 2mo ago First seen · 34 lines · 146 tokens per session scan A ea7f7c12abb3
Create database migration is a skill published in the GitHub repository TryGhost/Ghost (55,632 stars, last pushed today), licensed MIT. It adds 145 tokens to every session and 783 once invoked, about $0.0006 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
cms-metadata-tagger
Takes a finished piece of content and produces a complete, archive-ready metadata record — including descriptive tags, subject classifications, rights notes, and an archival summary — for entry into a content management or digital archive system.
cms-metadata-writer
Writes structured metadata fields — title tag, meta description, tags, category, slug, and Open Graph text — for a CMS entry, optimized for search discoverability and social sharing.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
record-upgrade-instructions
Record upgrade instructions alongside a Prisma 8 breaking-change PR, so downstream consumers (users of @internal/ and authors of Prisma 8 extensions) can apply the matching code translation automatically via the published upgrade skills. Use when you have refactored framework code and the test suite went red in…