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 agentmods add skills/gleanwork/pluginpack/migrate-to-pluginpacknpx skills add gleanwork/pluginpack --skill migrate-to-pluginpackgit clone --depth 1 https://github.com/gleanwork/pluginpackWhat 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 | $0.00078 | $0.00470 |
| Opus 5 | $0.00039 | $0.00235 |
| Sonnet 5 | $0.00016 | $0.00094 |
| Haiku 4.5 | $0.00008 | $0.00047 |
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 yesterday.
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
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 underplugins/<id>/withskills/,agents/,commands/,rules/,hooks/,assets/). Addplugin.pluginpack.jsonfor per-plugin metadata and a.mcp.jsonfor MCP servers. Where a file must differ per app, addtargets/<target>/<file>next to the base file. -
Write the config targeting that app, mapping source → emitted plugin via
from, andpath/pluginRootto 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-pluginsIterate on the source/config until
diffexits 0. For paths the generated repo legitimately owns (license, CI, hand-written README), add them to the target'signoredDiffPaths. -
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.
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.
- yesterday First seen · 43 lines · 78 tokens per session scan A 308b1be5f87e
migrate-to-pluginpack is a skill published in the GitHub repository gleanwork/pluginpack (5 stars, last pushed 21d ago), licensed MIT. It adds 78 tokens to every session and 470 once invoked, about $0.0004 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…