What is migrate-to-pluginpack?

A migration skill for turning an existing native plugin repository into a portable pluginpack source project. A plugin repository contains reusable extensions such as skills, commands, agents, hooks, or tool connections for a coding assistant.

It is for migrating Claude Code, Cursor, Antigravity CLI, GitHub Copilot, or OpenAI Codex CLI plugins into pluginpack, then building and comparing the generated output.

It replaces separate hand-maintained copies with one source layout that can generate the required format for different coding tools and verify the generated files against the original.

migrate-to-pluginpack — Skill for Claude Code and Codex by gleanwork

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/gleanwork/pluginpack

agentmods

npx agentmods add skills/gleanwork/pluginpack/migrate-to-pluginpack

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gleanwork/pluginpack/migrate-to-pluginpack/github.svg)](https://agentmods.dev/skills/gleanwork/pluginpack/migrate-to-pluginpack)

Your own site

<a href="https://agentmods.dev/skills/gleanwork/pluginpack/migrate-to-pluginpack"><img src="https://agentmods.dev/badge/skills/gleanwork/pluginpack/migrate-to-pluginpack/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gleanwork/pluginpack/migrate-to-pluginpack"><img src="https://agentmods.dev/badge/skills/gleanwork/pluginpack/migrate-to-pluginpack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 470 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00078	$0.00470
Opus 5.5	$0.00031	$0.00188
Sonnet 5.5	$0.00016	$0.00094
Haiku 4.5	$0.00008	$0.00047

Measured 1mo ago against content hash 308b1be5f87e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

migrate-to-pluginpack 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.

skills/migrate-to-pluginpack/SKILL.md · 43 lines

What it actually says

Migrating an existing plugin repo into pluginpack

Goal: stop hand-maintaining a native plugin repo by generating it from portable source, verified byte-for-byte against the original.

Steps

Inspect the existing repo. Note its marketplace manifest (.claude-plugin/marketplace.json, .cursor-plugin/marketplace.json, .codex-plugin/plugin.json, …), the per-plugin layout, and the skill/agent/command/hook/MCP content.
Create portable source. Put skills under a repo-level skills/ directory (or richer plugins under plugins/<id>/ with skills/, agents/, commands/, rules/, hooks/, assets/). Add plugin.pluginpack.json for per-plugin metadata and a .mcp.json for MCP servers. Where a file must differ per app, add targets/<target>/<file> next to the base file.
Write the config targeting that app, mapping source → emitted plugin via from, and path/pluginRoot to reproduce the original directory layout. See the authoring-pluginpack-config skill.
Build and diff until clean:
```
pluginpack build --target claude
pluginpack diff --target claude --against ../claude-plugins
```
Iterate on the source/config until diff exits 0. For paths the generated repo legitimately owns (license, CI, hand-written README), add them to the target's ignoredDiffPaths.
Wire diff into CI in the generated repo so future source changes that aren't regenerated are caught.

Tip: migrate one target at a time; diff is the source of truth for fidelity.

Changes

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 · 43 lines · 78 tokens per session scan A 308b1be5f87e

Subscribe to this mod's changes

migrate-to-pluginpack is a skill published in the GitHub repository gleanwork/pluginpack (6 stars, last pushed 3d ago), licensed MIT. It adds 78 tokens to every session and 470 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-31.

Building agents

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens