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/migrate-internal-package/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/migrate-internal-package)<a href="https://agentmods.dev/skills/tryghost/ghost/migrate-internal-package"><img src="https://agentmods.dev/badge/skills/tryghost/ghost/migrate-internal-package/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/migrate-internal-package"><img src="https://agentmods.dev/badge/skills/tryghost/ghost/migrate-internal-package.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- 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.00077 | $0.03009 |
| Opus 5.5 | $0.00031 | $0.01204 |
| Sonnet 5.5 | $0.00015 | $0.00602 |
| Haiku 4.5 | $0.00008 | $0.00301 |
Grade A, and why
migrate-internal-package 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.
How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate an internal package into Ghost
Move a package from another TryGhost repository into Ghost without losing its history or creating a period where neither repository owns it. Keep migration mechanics separate from Ghost's lifetime package standards.
Any contributor can run this skill. Do not require repository administration permission for the audit, import, PR preparation, CI, read-only preflight, post-merge verification or follow-up work. Administration is required only at the exceptional merge checkpoint, which is handed to one of the small set of Ghost repository administrators.
The contributor workflow is documented in
docs/contributing/internal-package-migrations.md.
Keep that guide aligned when this skill changes its outputs or human
checkpoints.
Authority boundaries
Explain every cross-repository or administrative action before it happens.
- A request for instructions is not permission to perform the action.
- If the user says "tell me how, I do it", provide the command and wait.
- Require explicit authorization before changing repository settings, merging a PR, deprecating npm versions, or force-pushing.
- Never run the history import's
--confirmoperation. That command is the deliberate human administrator checkpoint because it temporarily changes a Ghost repository setting and merges the exceptional PR. - Never ask for, display, or store credentials or OTPs.
Work in isolated checkouts
Never manipulate history in a checkout containing unrelated work. Fetch both
repositories, confirm the source checkout is clean, and create a dedicated
Ghost worktree from the freshly fetched origin/main.
Run history-changing commands individually or in a fail-fast shell. A failed
git worktree add must not be followed by git subtree add in whichever
checkout happens to be current. Before choosing a branch or path, list existing
worktrees and matching local and remote branches. Use a migration-specific slug,
for example codex/import-<package>-from-<source>, rather than a generic name.
What ships with it
3 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.
- 1mo ago Changed · +8 lines 598f0a665bff
- 1mo ago Changed · +54 lines e783ec6c383c
- 2mo ago First seen · 245 lines · 77 tokens per session scan A 3886cd778294
migrate-internal-package is a skill published in the GitHub repository TryGhost/Ghost (55,632 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 3,009 once invoked, about $0.0003 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…
triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…