It is for teams and solo builders who want real plugin repos, shared workflows, and a cleaner path than one-off scripts or duplicated config files.

Install plugin-kit-ai, create a plugin repo with init, then run render and validate --strict. After that, grow into more supported outputs only when the product needs them.

Yes. The toolkit is open source, and this landing page is the front door for both the toolkit and the first-party plugin catalog we are building on top of it.

P plugin-kit-ai

Build a plugin once. Ship it to multiple AI agents from one repo. plugin-kit-ai is the home for our first-party plugin lineup and the open-source toolkit behind it.

Open GitHub See plugins View docs

Latest release · v1.0.6 · Mar 30, 2026

First-party plugins coming soon

One repo

Clear workflow

Open Source

Keep one plugin repo as the source of truth instead of copying the same logic into separate agent-specific folders.

Begin with the output that matters now, then expand to more supported agents when your product actually needs it.

Use a repeatable render and validate flow before another teammate, CI job, or end user touches the plugin.

plugin-kit-ai is explicit about what is production-ready, what is public beta, and where you should not promise fake parity yet.

Homebrew, npm, pipx when published, verified install script, GitHub releases, and docs all point to one clean starting flow.

Use the toolkit today, inspect the source, and follow a transparent workflow while our first-party plugin catalog grows.

First-party plugin concept

Review Guard

Coming soon

Flag risky tool usage, missing checks, and policy drift before a plugin reaches another teammate or customer.

Supports

ClaudeCodexGemini

First-party plugin concept

Release Notes Builder

Coming soon

Turn commits, diffs, and handoff context into clear release notes and changelog drafts for fast publishing.

Supports

CodexClaudeOpenCode

First-party plugin concept

Docs Sync

Coming soon

Keep README files, docs pages, and support notes aligned with what actually changed in the repo.

Supports

ClaudeCodexCursor

First-party plugin concept

Repo Onboarding

Coming soon

Set up contributor guidance, repo instructions, and agent-ready context so new people can start faster.

Supports

ClaudeCursorOpenCode

First-party plugin concept

Command Safety

Coming soon

Block unsafe command patterns, offer safer alternatives, and make approval-sensitive operations easier to review.

Supports

CodexClaudeGemini

First-party plugin concept

Workspace Setup

Coming soon

Prepare agent-specific config, workspace wiring, and shared defaults from one managed source repo.

Supports

OpenCodeCursorGemini

Recommended quickstart

This is the fastest supported path from install to a validated repo.

Install the CLI

Command

brew install 777genius/homebrew-plugin-kit-ai/plugin-kit-ai
plugin-kit-ai version

Homebrew is the recommended local install path for the CLI itself.

Create the strongest default repo first

Command

plugin-kit-ai init my-plugin
cd my-plugin

The default path starts with the strongest supported production story.

Render managed target files

Command

plugin-kit-ai render .

Generate the managed target artifacts from one authored repo.

Validate before handoff

Command

plugin-kit-ai validate . --platform codex-runtime --strict

Use the strict validation gate before CI, teammate handoff, or release.

Support snapshot

Real support depth today, based on the current support policy and target matrix.

Claude plugin package

Production-ready stable subset

Production-ready within the stable default hook subset, plus package metadata and settings surfaces.

Codex runtime and package lanes

Production-ready

Codex runtime notify lane and the official Codex package lane are both production-ready.

Gemini extension lane

Public beta

Extension packaging is supported, but the overall lane is still not production-ready.

OpenCode workspace lane

Packaging-only target

Workspace config, plugins, and MCP are supported, but this is not a production-ready runtime target.

Cursor workspace lane

Packaging-only target

Project rules and MCP config are supported as a strict workspace-config lane.

Read the support boundary

Homebrew

Recommended

Recommended local install for machines that already use Homebrew.

Command

brew install 777genius/homebrew-plugin-kit-ai/plugin-kit-ai

Best default when Homebrew is available.

Open

npm

Official JavaScript ecosystem wrapper for teams that already center their workflow on npm.

Command

npm i -g plugin-kit-ai

Public-beta wrapper that downloads the matching verified release binary.

Open

pipx

Python ecosystem wrapper when the corresponding release is published to PyPI.

Command

pipx install plugin-kit-ai

Public-beta wrapper. Use this channel only when the target release is available on PyPI.

Open

Verified install script

Fallback bootstrap path that resolves the latest published stable release and verifies checksums.

Command

curl -fsSL https://raw.githubusercontent.com/777genius/plugin-kit-ai/main/scripts/install.sh | sh

Good when package-manager setup is not what you want first.

Open

GitHub Releases

Browse published release notes, artifacts, and version history directly.

Command

https://github.com/777genius/plugin-kit-ai/releases

Use this when you want the raw release surface.

Open

Docs quickstart

Jump straight into the quickstart and the broader docs site.

Command

plugin-kit-ai init my-plugin

Best next step once the CLI is installed.

Open

One repo for many agent outputs

✓One source of truth

✕New setup per agent

◐Possible, but drifts fast

✕Usually one local flow only

Validation before handoff

✓Built around validate --strict

◐Depends on human review

◐Same check repeated everywhere

✕Easy to miss edge cases

Clear stable vs beta boundary

✓Documented and explicit

✕Usually tribal knowledge

✕Ambiguity gets copied too

✕No shared contract

Add outputs later without starting over

✓Grow from the same repo

◐Possible, but rework-heavy

✕Every new output starts from scratch

✕Usually a rewrite

Clear install and release channels

✓Docs, releases, and install paths line up

✕You assemble the flow yourself

◐Possible, but repeated work

✕Mostly local and ad hoc

Team-friendly onboarding

✓Shared workflow and examples

◐Lives in people and chat

✕More files, same confusion

✕Hard to hand off cleanly

What is plugin-kit-ai?

Who is this for?

What does “build once, ship to many agents” mean?

Is every supported output equally stable today?

How do I start?

Is it open source?

P plugin-kit-ai

A clean path from one plugin repo to many agents

One repo instead of scattered setup

Start with one strong path, add more later

Validate before handoff

Honest stable vs beta boundary

Clear install and release path

Open source from day one

Our first plugins start here

Review Guard

Release Notes Builder

Docs Sync

Repo Onboarding

Command Safety

Workspace Setup

Get started

Recommended quickstart

Install the CLI

Create the strongest default repo first

Render managed target files

Validate before handoff

Support snapshot

Claude plugin package

Codex runtime and package lanes

Gemini extension lane

OpenCode workspace lane

Cursor workspace lane

Homebrew

npm

pipx

Verified install script

GitHub Releases

Docs quickstart

Why it works

Got questions? We've got answers