Menu
Discover, evaluate, install, test, and manage agent plugins for VS Code Copilot
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Health check procedures D1–D14 for the Audit agent — structural validation, attention budget, version checks, workspace integrity, and static audit
Configure and manage Model Context Protocol servers for external tool access
Review a UI for accessibility — WCAG 2.1 AA compliance, semantic HTML, ARIA usage, keyboard navigation, focus management, colour contrast, and screen reader compatibility
Design or review a REST or GraphQL API — resource modeling, versioning strategy, error contract, OpenAPI/schema-first workflow, and security baseline
Generate a CHANGELOG.md entry from staged changes, a commit range, or a PR diff — following Keep a Changelog format with conventional commit classification
Set up and audit environment variable management — create .env.example, add startup validation, separate secrets from config, and document every variable
| name | plugin-management |
| description | Discover, evaluate, install, test, and manage agent plugins for VS Code Copilot |
| compatibility | >=3.2 |
Skill metadata: version "1.1"; license MIT; tags [plugins, agents, extensions, discovery, management]; compatibility ">=3.2"; recommended tools [codebase, runCommands, editFiles].
Agent plugins (VS Code 1.110+, Preview) are installable packages that bundle agents, skills, hooks, MCP servers, and slash commands. This skill covers discovering, evaluating, installing, testing, and managing plugins alongside the template's own customization files.
A single plugin can bundle any combination of:
| Type | Description |
|---|---|
| Slash commands | Additional / commands in chat |
| Skills | Agent skills with instructions, scripts, and resources |
| Agents | Custom agents with specialized personas and tool configurations |
| Hooks | Shell commands at agent lifecycle points (hook config in hooks/hooks.json or hooks.json) |
| MCP servers | External tool integrations (config in .mcp.json at plugin root, uses mcpServers key) |
User wants a plugin
│
├─ 1. CHECK INSTALLED — list installed plugins
│ Run in Extensions view: filter @agentPlugins
│ Or check VS Code settings for chat.pluginLocations (local plugins)
│ ├─ Found → verify it meets the need → DONE
│ └─ Not found → ↓
│
├─ 2. SEARCH — find plugins in configured marketplaces
│ Extensions view → search @agentPlugins <keyword>
│ Or browse chat.plugins.marketplaces URLs
│ Default marketplaces: github/copilot-plugins, github/awesome-copilot
│ Additional: anthropics/claude-code
│ ├─ Found → evaluate (see Quality Gate below) → install
│ └─ Not found → ↓
│
├─ 3. INSTALL FROM SOURCE — install directly from a Git URL
│ Command: Chat: Install Plugin From Source
│ Or: select + button on Plugins page of Chat Customizations editor
│
└─ 4. RECOMMEND ALTERNATIVE — no suitable plugin exists
Consider: workspace skill (.github/skills/), MCP server, or custom tool
Before recommending or installing a plugin, verify:
Plugins failing two or more checks are rejected.
When a plugin contributes an agent or skill with the same name as a workspace file:
| Conflict type | Resolution |
|---|---|
| Agent name collision | Workspace agent takes priority. VS Code shows source in tooltip. |
| Skill name collision | Project skills (.github/skills/) override plugin skills. |
| Hook collision | Workspace hooks fire alongside plugin hooks — check for duplicate behaviour. Most restrictive PreToolUse decision wins. |
| MCP server collision | Plugin MCP servers run alongside workspace servers. Disable via plugin toggle. |
Use the Agent Debug Panel (Developer: Open Agent Debug Panel) to see exactly which agents, skills, and hooks are loaded and from which source.
Plugins can include hooks that fire at lifecycle events (SessionStart, PreToolUse, PostToolUse, PreCompact, SubagentStart, SubagentStop, Stop).
hooks/hooks.json (Claude format) or hooks.json (Copilot/OpenPlugin format)${CLAUDE_PLUGIN_ROOT} for Claude-format plugins and ${PLUGIN_ROOT} for OpenPlugin plugins${CLAUDE_PLUGIN_ROOT} exists there.Plugins can bundle MCP servers that start automatically when the plugin is enabled.
.mcp.json at plugin root using mcpServers key (not servers)${CLAUDE_PLUGIN_ROOT} for Claude-format plugins and ${PLUGIN_ROOT} for OpenPlugin plugins| Setting | Purpose |
|---|---|
chat.plugins.enabled | Enable/disable plugin discovery (boolean) |
chat.plugins.marketplaces | Git repositories serving as plugin marketplaces (array of owner/repo) |
chat.pluginLocations | Local paths for plugin development/testing (map of path → boolean) |
Projects can recommend plugins for team members:
{
"extraKnownMarketplaces": {
"company-tools": {
"source": { "source": "github", "repo": "your-org/plugin-marketplace" }
}
},
"enabledPlugins": {
"code-formatter@company-tools": true
}
}
To preview how the template's agents, skills, hooks, and prompts appear as plugin-contributed customizations:
Clone the template repo (or use an existing local copy)
Add to VS Code settings:
"chat.pluginLocations": {
"/path/to/copilot-instructions-template": true
}
Reload VS Code — plugin-contributed agents appear in the Copilot dropdown
Verify: open the Agent Debug Panel to confirm agents, skills, and hooks are loaded
Check for conflicts with any workspace-level agents in .github/agents/
@agentPlugins to see all installed pluginsExtensions: Check for Extension Updates or automatic every 24 hours