dsh-agent-plugin-bridge

The Agent Plugins 1.0 ecosystem is growing fast—tm-dagu-adapt, agenthandoff, and whatever the next agent-plugins.org package is—but every new integration has meant writing bespoke glue code, repeating the same wiring logic over and over. dsh-agent-plugin-bridge replaces that pattern with a single generic code path: drop it into any DSH profile and on startup it scans your configured plugin roots and directories, finds every package carrying a valid plugin.json, registers its skills/ SKILL.md files into the host skills service, and registers its mcp.json into the host MCP client. A new conformant package simply works—no per-package adapter to maintain.

The bridge also handles the real-world friction that trips up integrators. mcp.json files frequently use ${SOME_ENV} placeholders that resolve to an empty command when the host lacks the variable, so the plugin exposes a loadPluginMcp toggle and an mcpJsonPaths list for standalone files like ~/.cursor/mcp.json, letting user-level MCP config stay alive even before plugin-specific env vars are in place. A runtime peer-version guard turns pnpm's tendency to silently link an older RC into a loud, actionable error rather than a quiet background failure. The bridge_summary tool it registers lets you ask the agent at any moment exactly which skills and MCP servers were loaded, turning a debugging session into a one-liner.

Built for DSH developers adopting the Agent Plugins 1.0 spec with minimal friction, engineering teams juggling multiple agent plugin packages without maintaining per-package adapters, and groups that want packaged-integration tests plus a DSH-boot smoke job in CI to catch load-time regressions before they reach a production profile.