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-service/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-service)<a href="https://agentmods.dev/skills/tryghost/ghost/migrate-service"><img src="https://agentmods.dev/badge/skills/tryghost/ghost/migrate-service/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-service"><img src="https://agentmods.dev/badge/skills/tryghost/ghost/migrate-service.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.00056 | $0.02022 |
| Opus 5.5 | $0.00022 | $0.00809 |
| Sonnet 5.5 | $0.00011 | $0.00404 |
| Haiku 4.5 | $0.00006 | $0.00202 |
Grade A, and why
migrate-service 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 4d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate one service
Prepare a small, behavior-preserving migration of one existing service. This is an execution workflow, not the final service-authoring guide or permission to redesign a service's lifecycle. Read current repository guidance rather than copying an earlier migration blindly.
1. Establish the starting point
- Read the root and nearest
AGENTS.md, the services guide, kernel contract, testing guide and contribution workflow. - Inspect status, existing branches/worktrees and related PRs. Preserve unrelated
work. Fetch
originand start from currentorigin/main; refresh dependencies withpnpm bootstrapin a fresh checkout or after dependency changes. - Read this service's entry in
ghost/core/server/services/service-inventory.yamland any existing migration plan. If a plan-registry skill is available, use it to find/update that plan; do not create a competing plan in the repository. - Verify prerequisites are merged. An open tests or enforcement PR is not main. Preparation can proceed against a proposed policy, but record its exact head and repeat validation against the policy that actually merges.
2. Audit the whole service and its callers
Use rg across production and tests. Include deep imports, nested helpers,
separate actions, job handlers, CLI use and CommonJS consumers. Also inspect
shared boot harnesses and tests that construct routers or renderers indirectly;
a search for the service name alone misses those fixtures. Record:
- Existing runtime/type exports and the intended instance and extras surfaces.
- Who constructs each instance and whether consumers capture it during import.
- Dependencies acquired at import, boot, request, dispatch and job execution.
- Configuration captured once versus read again for each operation.
- Shared identity, caches, pending/rejected promises and invalidation semantics.
- Resource ownership, partial-startup cleanup, normal shutdown and failure policy.
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.
- 4d ago Changed · +19 lines b8af0b73eb70
- 7d ago Changed · +12 lines b820f5d4c6b9
- 14d ago First seen · 139 lines · 56 tokens per session scan A 5607d75207ec
migrate-service is a skill published in the GitHub repository TryGhost/Ghost (55,632 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 2,022 once invoked, about $0.0002 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-10-16.
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.
reviewing-blogs
Reviews and critiques blog posts in src/content/blog/posts/ against Appwrite's established standards for voice, tone, structure, SEO, formatting, and accuracy. Use when the user asks to review, audit, critique, or improve an existing blog post.
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.
creating-plugins
Create EmDash CMS plugins with sandboxed hooks, routes, storage, content and media APIs, MCP tools, and declarative admin UI, or native React and Astro extensions. Use when scaffolding or implementing an EmDash plugin.
ax-go-flow
Use when writing Go code with github.com/ax-llm/ax/packages/go for flows, nodes, program graphs, nested programs, dynamic options, caching, and optimizer components.