A tool-neutral agent-plugin marketplace that bundles curated agent skills — sourced from across the agent-skill ecosystem — into category-based plugins.
Supports VS Code, GitHub Copilot CLI, and Claude Code via dual marketplace manifests.
This is a tool-neutral plugin marketplace, not a skills-only bundler. Every plugin published today bundles agent skills, but a plugin may bundle any agent resource — skills, MCP servers, and custom agents — so the marketplace can grow with the cross-tool agent ecosystem instead of being pinned to one tool or one resource type. Additional resource types are added as they prove out across the supported tools.
| Plugin | Resources | Description |
|---|---|---|
gitops-kubernetes |
gitops-cluster-debug, gitops-knowledge, gitops-repo-audit, gitops-tenant-onboarding (skills) · flux-operator-mcp (MCP server) · flux-troubleshooter (agent) |
Flux CD debugging, knowledge, repository auditing, and tenant onboarding — bundles the Flux MCP server and a read-only Flux troubleshooter agent for live-cluster debugging |
github |
gh-cli, gh-stack, github-actions-docs, github-issues |
GitHub CLI, stacked PRs, Actions docs, and issue management |
agentic-engineering |
agent-instructions, copilot-instructions-blueprint-generator, copilot-sdk, find-skills |
Agentic AI framework SDKs, AI-assistant instruction authoring, and skill discovery |
go |
golang-pro |
Go best practices, concurrency, generics, interfaces, and testing |
engineering-practices |
conventional-release, git-commit, refactor, test-driven-development, ways-of-working |
Git commits, conventional releases, refactoring, TDD, and engineering ways of working |
frontend-design |
astro, frontend-design, web-design-guidelines |
Astro, frontend design, and web design guidelines |
Add the marketplace to your settings:
Then browse Extensions → Agent Plugins (@agentPlugins search) to install individual plugins.
# Browse available plugins
copilot plugin marketplace browse devantler-tech/agent-plugins
# Install a plugin
copilot plugin install gitops-kubernetes@devantler-pluginsAdd the marketplace, then install a plugin — run these inside Claude Code:
/plugin marketplace add devantler-tech/agent-plugins
/plugin install gitops-kubernetes@devantler-plugins
Browse everything on offer with /plugin (Discover tab) or list it with /plugin list. The bundled .claude-plugin/marketplace.json is also discovered automatically when this repo is added as a plugin source.
A plugin may bundle MCP servers as well as skills. The
gitops-kubernetes plugin bundles the Flux MCP server
(flux-operator-mcp)
so its gitops-cluster-debug skill — which Requires flux-operator-mcp — works against a live
cluster out of the box.
The server is authored once as the plugin's .mcp.json
(mcpServers map). How each tool consumes it differs (per ADR 0001):
-
Claude Code and Copilot CLI — the bundled
.mcp.jsonis loaded automatically when the plugin is installed; no extra configuration is needed. -
VS Code consumes MCP but does not bundle it from a plugin. Add the equivalent entry to your workspace
.vscode/mcp.json(note the key isservers, notmcpServers):{ "servers": { "flux-operator-mcp": { "command": "flux-operator-mcp", "args": ["serve"] } } }
All three paths invoke the same flux-operator-mcp binary, so install it first — e.g.
brew install controlplaneio-fluxcd/tap/flux-operator-mcp or go install github.com/controlplaneio-fluxcd/flux-operator/cmd/mcp@latest (it reads your kubeconfig from
KUBECONFIG / ~/.kube/config). See the
Flux MCP docs for read-only mode and remote
transport.
A plugin may also bundle custom agents (subagents). The
gitops-kubernetes plugin bundles
flux-troubleshooter — a read-only
Flux CD triage agent that traces the GitOps dependency chain (source → Kustomization/HelmRelease →
workloads), reads status conditions and controller logs via the bundled flux-operator-mcp server,
and returns a root-cause diagnosis plus the human-applied fix. It has no apply/reconcile/suspend/
delete tool by design, so it never mutates the cluster.
The agent is authored once as agents/<name>.md (Markdown + YAML frontmatter, with the neutral
name/description/tools/model core). How each tool consumes it differs (per
ADR 0001):
- Claude Code and Copilot CLI — the bundled
agents/directory is loaded automatically when the plugin is installed; the agent is namespacedgitops-kubernetes:flux-troubleshooter. (Copilot reads the same file as*.agent.md.) - VS Code consumes agents but does not bundle them from a plugin. Copy the agent to your
workspace as
.github/agents/flux-troubleshooter.agent.md.
Skills are installed from their upstream repositories using gh skill install. A daily update workflow runs gh skill update --all via the update-agent-skills reusable workflow and opens a PR when upstream content has drifted.
Each plugin directory is self-contained with a plugin.json manifest and its bundled resources — a skills/ subdirectory holding the installed SKILL.md files (plus any supporting assets), and optionally an .mcp.json declaring bundled MCP servers and an agents/ directory holding custom agents. Each SKILL.md contains metadata.github-* frontmatter for upstream provenance — no lockfile needed.
Each bundled skill is pulled from its own upstream (recorded in its SKILL.md metadata.github-* frontmatter), spanning many sources — including our in-house sibling library devantler-tech/agent-skills.
See the devantler-tech organisation guidelines for PR/issue templates and contribution rules.
Apache 2.0 — see LICENSE.