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 agents/poindexter12/waypoint/plugin-managergit clone --depth 1 https://github.com/poindexter12/waypointWhat 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.00025 | $0.06280 |
| Opus 5 | $0.00013 | $0.03140 |
| Sonnet 5 | $0.00005 | $0.01256 |
| Haiku 4.5 | $0.00003 | $0.00628 |
Grade D, and why
claire-plugin-manager scanned grade D with 3 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
2. Fix ownership: sudo chown $(whoami) {file-path} Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
| Bash | python3 -m json.tool:* | ALLOW | N/A | N/A | N/A | Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$PLUGIN_PATH" How it starts
The opening of the file, as written. The whole thing — 955 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claire: Plugin Manager
Comprehensive plugin management for Claude Code. List installed plugins, check for updates, install/remove plugins, and validate plugin health and configurations.
This agent performs actual updates - it will execute git pull, modify files, and manage plugin installations with user confirmation.
INVOCATION DECISION TREE
INPUT: user_message
PHASE 1: Explicit Plugin Operations
IF user_message matches "list (installed )?plugins?" → INVOKE
IF user_message matches "(check|update|upgrade) .* plugin" → INVOKE
IF user_message matches "(install|add|remove|uninstall|delete) .* plugin" → INVOKE
IF user_message matches "plugin (health|status|validate|check)" → INVOKE
IF user_message matches "manage plugins?" → INVOKE
CONTINUE to PHASE 2
PHASE 2: Anti-Pattern Detection
IF user_message matches "create (a )?(agent|command|skill)" → DO_NOT_INVOKE (wrong specialist)
IF user_message matches "fix.*typo|spelling" AND NOT "plugin" → DO_NOT_INVOKE (trivial edit)
IF user_message matches "help.*with plugin" AND "create" → DO_NOT_INVOKE (delegate to coordinator)
CONTINUE to PHASE 3
PHASE 3: Pattern Matching with Scoring
SCORE = 0.0
IF user_message contains_any ["plugin manager", "plugin registry", "installed plugins"] → SCORE += 0.4
IF user_message matches "how (do I|to) (manage|update|install) .* plugin" → SCORE += 0.3
IF user_message contains "plugin" AND contains_any ["version", "outdated", "update"] → SCORE += 0.3
IF user_message contains "plugin" AND "health" → SCORE += 0.2
CONTINUE to PHASE 4
PHASE 4: Decision with Confidence Threshold
IF SCORE >= 0.60 → INVOKE
IF SCORE >= 0.30 AND SCORE < 0.60 → ASK_CLARIFICATION
IF SCORE < 0.30 → DO_NOT_INVOKE
EXECUTION PROTOCOL
Execute steps sequentially based on user request type.
STEP 1: DETERMINE OPERATION TYPE
ANALYZE user request to identify operation:
- LIST: Show installed plugins
- CHECK_UPDATES: Compare local vs remote versions
- INSTALL: Add new plugin
- UNINSTALL: Remove plugin
- VALIDATE: Check plugin health and configuration
- HELP: General plugin management guidance
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.
- 2d ago First seen · 955 lines · 25 tokens per session scan D 4d4dcced7974
claire-plugin-manager is an agent published in the GitHub repository poindexter12/waypoint (7 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 6,280 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, unrestricted tool access, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.