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/dvkolm/claude-plugin-manager/opennpx skills add DVKolm/claude-plugin-manager --skill opengit clone --depth 1 https://github.com/DVKolm/claude-plugin-managerWrote 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/dvkolm/claude-plugin-manager/open)<a href="https://agentmods.dev/skills/dvkolm/claude-plugin-manager/open"><img src="https://agentmods.dev/badge/skills/dvkolm/claude-plugin-manager/open.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00392 |
| Opus 5 | $0.00016 | $0.00196 |
| Sonnet 5 | $0.00007 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
open 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.
What it actually says
Open Plugin Manager
Launch the Plugin Manager web UI in the user's browser.
Steps
- Check if server is already running:
Read the file ~/.claude/plugins/plugin-manager.json. If it exists, check if the PID in it is still alive:
- Linux/macOS:
kill -0 <pid> 2>/dev/null && echo "alive" || echo "dead" - Windows:
tasklist /FI "PID eq <pid>" 2>NUL | findstr <pid> >NUL && echo alive || echo dead
-
If alive: Tell the user the Plugin Manager is already running and provide the URL:
http://localhost:<port>(they'll need to open it in their browser — the token was already exchanged). -
If dead or file doesn't exist: Start the server:
node "${CLAUDE_PLUGIN_ROOT}/dist/server.js" &
Read the first line of output — it's a JSON object with url and port.
- Open as app window (no browser chrome — looks like a native widget):
- Windows:
start msedge --app="<url>"(Edge app mode, no address bar or tabs) - macOS:
open -a "Google Chrome" --args --app="<url>" - Fallback: Tell the user to open the URL in their browser manually.
Notes
- The server auto-exits after 30 minutes of inactivity
- The server binds to localhost only (127.0.0.1)
- Changes made in the UI take effect on the next Claude Code session
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 First seen · 37 lines · 33 tokens per session scan A 1b4e5d97d78a
open is a skill published in the GitHub repository DVKolm/claude-plugin-manager (2 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 392 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…