build-hermes-agent-extensionslisted

# Build Hermes Agent Extensions Choose the owned extension surface before creating files. Hermes uses several unrelated plugin and integration systems; do not force them into one generic package. ## Select the Surface 1. Use a skill for instructions, existing commands, and progressive disclosure. 2. Use MCP for an external tool server. 3. Use a general Python plugin for registered tools, lifecycle hooks, slash commands, CLI commands, or bundled namespaced skills. 4. Use a specialized provider/plugin surface for models, messaging platforms, memory, context engines, secrets, image/video generation, web search, or browser sessions. 5. Use configuration for TTS commands, STT commands, shell hooks, MCP, and other explicitly config-driven surfaces. 6. Use gateway hook directories for gateway event handlers. 7. Use the desktop SDK or dashboard SDK only for their respective UI host; they do not share the Python plugin API. 8. Use ACP when an editor or compatible client drives the agent; hand generic ACP implementation to `build-acp-agent` and existing client setup to `operate-acp-agent-integration`. 9. Use A2A when independently operated agents exchange discovered tasks; hand operation to `operate-a2a-agent-integration` and use Hermes's specialized platform adapter only when extending its native A2A surface. 10. Use TUI gateway JSON-RPC or the OpenAI-compatible API server for custom programs that drive the agent without an ACP client. 11. Modify Hermes core only when the fea