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/benwilcock/rhdh-lab/dynamic-pluginsnpx skills add benwilcock/rhdh-lab --skill dynamic-pluginsgit clone --depth 1 https://github.com/benwilcock/rhdh-labWrote 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/benwilcock/rhdh-lab/dynamic-plugins)<a href="https://agentmods.dev/skills/benwilcock/rhdh-lab/dynamic-plugins"><img src="https://agentmods.dev/badge/skills/benwilcock/rhdh-lab/dynamic-plugins.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.00019 | $0.02195 |
| Opus 5 | $0.00010 | $0.01097 |
| Sonnet 5 | $0.00004 | $0.00439 |
| Haiku 4.5 | $0.00002 | $0.00219 |
Grade A, and why
dynamic-plugins 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dynamic Plugin System
Critical: Override REPLACES, Not Merges
The dynamic-plugins.override.yaml file replaces the base dynamic-plugins.yaml via a
symlink created by prepare-and-install-dynamic-plugins.sh. It does NOT merge with it.
Consequence: Every plugin you want enabled must appear in your override file (or be pulled
in via includes). Any plugin not listed is effectively disabled -- even plugins that ship
enabled by default (like Lightspeed in RHDH 1.10+).
Plugin Configuration Files
dynamic-plugins.default.yaml-- Generated from the catalog index image at install time; provides version data for{{inherit}}resolution. NEVER edit.dynamic-plugins.yaml-- Base plugin list fromrhdh-local/. NEVER edit (it gets symlinked to the override).dynamic-plugins.override.yamlinrhdh-customizations/configs/dynamic-plugins/-- The only file you edit. This becomes the sole plugin configuration.dynamic-plugins.extensions.yaml-- Generated at runtime by the Extensions UI. Saved to a separate path to avoid overwriting the override.
The {{inherit}} Version Tag
Use {{inherit}} for Red Hat registry OCI plugins. The installer resolves the version
from dynamic-plugins.default.yaml (generated from the catalog index image).
Benefits: Versions auto-update when the RHDH container image or catalog index changes (e.g. new RHDH release). No manual version hunting or SHA256 digest management.
Requires: includes: - dynamic-plugins.default.yaml in the override file. Without this
include, {{inherit}} resolution fails with an InstallException.
Works for (plugins listed in dynamic-plugins.default.yaml):
- Red Hat registry plugins:
oci://registry.access.redhat.com/rhdh/...:{{inherit}}(Lightspeed, Orchestrator, and other Red Hat-shipped plugins)
Does NOT work for (not in dynamic-plugins.default.yaml):
- Community plugins from ghcr.io export-overlays -- these require explicit version tags
(e.g.
bs_1.49.4__3.7.0) - Local
./dynamic-plugins/dist/plugins (ship with the container, no version needed)
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.
- 5d ago First seen · 226 lines · 19 tokens per session scan A f4cc04895251
dynamic-plugins is a skill published in the GitHub repository benwilcock/rhdh-lab (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 2,195 once invoked, about $0.0001 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.
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…
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…