Multi-agent
One repository serves Claude Code, GitHub Copilot, OpenAI Codex and Cursor. The plugin content is shared across all of them.
AGent marketplace KIT
agkit scaffolds and manages plugin marketplaces for
Claude Code, GitHub Copilot, OpenAI Codex
and Cursor — one canonical catalog, distributed through
any Git forge with a plain git push.
npm install -g agkit
npx agkit — nothing to installWhy agkit
ng for Angular — but for agent plugin marketplacesinit gives you a push-ready repository; add, build, sync, bump and validate cover the whole life of the project afterwards.
One repository serves Claude Code, GitHub Copilot, OpenAI Codex and Cursor. The plugin content is shared across all of them.
Distribute via GitHub, GitLab, Bitbucket, Gitea or self-hosted — with a plain git push. No registry account, no lock-in.
A single canonical .claude-plugin/marketplace.json. Generated registries derive from it — and never drift.
init · add · build · sync · bump · validate · list — from first scaffold to versioned releases with changelogs.
Catalog a remote plugin by reference (no clone), vendor a template into your repo with --vendor, or scaffold from built-in templates.
Generated GitHub Actions / GitLab CI out of the box, with validate and build --check gates that fail on drift.
How it works
agkit always writes one canonical catalog plus your plugins. How each agent reads it falls into three groups: native, generated by agkit build, or not supported yet. New to this? Start with what a plugin marketplace is.
Claude Code and GitHub Copilot read .claude-plugin/marketplace.json directly. Push the repo and it installs.
agkit buildCodex and Cursor install from their own committed registry, derived from the same catalog. Run build once; add / bump / sync keep it fresh automatically.
Gemini, OpenCode, Windsurf and Kiro can be passed to --agents, but nothing is generated for them — a marketplace is not installable from these agents today. They have no registry concept, so supporting them means a different distribution model, not just another generator.
Quick start
Requires Node.js ≥ 22. Run it on demand with npx — nothing to install.
init targets Claude Code and GitHub Copilot by default; add --agents codex,cursor to serve more. --agents also accepts gemini, opencode, windsurf and kiro, but those are recorded as intent only — nothing is generated and consumers cannot install from them yet.
Commands
agkit initScaffolds a git-first marketplace: catalog, plugins/, per-agent README, team settings, CI. --plugin scaffolds a standalone plugin instead.
agkit addRegisters a plugin: reference a remote repo (no clone), vendor it with --vendor, or scaffold from a template — skill, command, agent, hook, mcp.
agkit buildGenerates the Codex and Cursor registries from the catalog. --check fails on drift — made for CI.
agkit syncReconciles the catalog with what's on disk: adds missing entries, fixes drift, flags orphans, regenerates docs and registries.
agkit bumpBumps a plugin version from conventional commits, prepends a dated CHANGELOG.md entry, and can commit + tag with --tag.
agkit validateLocal checks plus delegation to claude plugin validate when available. Non-zero exit on error — CI-ready.
agkit listLists the available plugin templates, built-in and local.
Adding plugins
A plugin can live inside your marketplace or stay in its own repo, fetched at install time. agkit add handles every case.
Catalog a remote plugin by reference — nothing is cloned; the agent fetches it at install time. Pin with --ref / --sha.
agkit add acme/deploy-plugin deploy
Clone a remote template into your repo so the plugin lives — and releases — with your marketplace.
agkit add gh:org/templates/kata kata --vendor
Start from a built-in or local template — or create a standalone plugin, no marketplace, with init --plugin.
agkit add skill tdd-coach
FAQ
agkit is an open-source CLI (npm package) that scaffolds and manages plugin marketplaces for AI coding agents. Think ng for Angular, but for agent plugin marketplaces: init gives you a push-ready repository, and add, build, sync, bump and validate cover the whole life of the project afterwards.
One repository serves Claude Code, GitHub Copilot, OpenAI Codex and Cursor. Claude Code and GitHub Copilot read the canonical catalog natively; for Codex and Cursor, agkit build generates their committed registries from the same catalog. Gemini, OpenCode, Windsurf and Kiro are accepted by --agents but recorded as intent only — no artifacts are generated, so a marketplace is not installable from these agents yet.
Not for Claude Code or GitHub Copilot — they read .claude-plugin/marketplace.json as-is. For OpenAI Codex and Cursor, run agkit build once; after that, add, bump and sync keep the generated registries fresh automatically.
Yes. agkit is forge-agnostic by design: distribute via GitHub, GitLab, Bitbucket, Gitea or any self-hosted Git forge with a plain git push. On github.com it uses the owner/repo shorthand; everywhere else it emits the git URL form, which every supported agent accepts.
With their agent's own command. Claude Code: /plugin marketplace add owner/repo then /plugin install name@marketplace. GitHub Copilot: copilot plugin marketplace add. OpenAI Codex: codex plugin marketplace add. Cursor: add the marketplace, then install the plugin by name.
Yes — agkit is MIT-licensed and free to use. It requires Node.js ≥ 22, and you can run it without installing via npx agkit. It is an unofficial community tool, not affiliated with Anthropic, GitHub, OpenAI or Cursor.