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 skills add gleanwork/pluginpack --skill add-pluginpack-targetgit clone --depth 1 https://github.com/gleanwork/pluginpackWrote 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/gleanwork/pluginpack/add-pluginpack-target)<a href="https://agentmods.dev/skills/gleanwork/pluginpack/add-pluginpack-target"><img src="https://agentmods.dev/badge/skills/gleanwork/pluginpack/add-pluginpack-target/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/gleanwork/pluginpack/add-pluginpack-target"><img src="https://agentmods.dev/badge/skills/gleanwork/pluginpack/add-pluginpack-target.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.00053 | $0.00510 |
| Opus 5.5 | $0.00021 | $0.00204 |
| Sonnet 5.5 | $0.00011 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
add-pluginpack-target 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.
What it actually says
Adding a pluginpack target
A target adapter owns one app's native layout, manifests, and validation.
First: get the real format, do not guess
Find the app's actual plugin format from official docs or a real published
plugin repo (the way the existing adapters were derived from github/copilot-plugins,
gleanwork/cursor-plugins, the Claude plugins reference, and the documented
OpenAI Codex CLI plugin format). Capture an
external oracle you can validate against — a published JSON Schema, the app's
own validator CLI, or a real repo to diff against. Record it in
CONFORMANCE.md.
Touch points
Adding a target means:
src/types.ts— add the name to theTargetNameunion.src/targets/<name>.ts— implementPluginTargetDefinition(seesrc/targets/types.ts): emit logic, manifest/marketplace builder, validation, install snippet, and defaults.src/targets/registry.ts— add one entry mapping the name to that definition.
Everything else — the CLI's --target choices, build()'s target set, and
emit/validate dispatch — derives from the registry automatically via the
shared engine in src/targets/engine.ts. Reuse src/targets/validation-shared.ts
for checks whose shape genuinely matches the other targets (hooks, frontmatter);
write your own where the shape is genuinely different, the way codex's
structured source object does.
Wire MCP
If the app supports MCP servers, decide whether it reads a .mcp.json file
(reference it from the manifest, like cursor/copilot, or rely on auto-discovery,
like claude), a target-specific config file (like Antigravity's
mcp_config.json), or another native shape. resolveMcpServers already merges
a plugin's servers; thread the result into your emitter.
Verify
Add conformance tests in tests/ against the external oracle, extend
CONFORMANCE.md, then run npm run check.
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 · 50 lines · 53 tokens per session scan A b39385f55ca4
add-pluginpack-target is a skill published in the GitHub repository gleanwork/pluginpack (6 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 510 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-08-31.
Other skills, from other repositories
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…
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…
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.
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…
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…