agentbundler

README

Agent Bundler

One source → target-specific coding-agent layouts

Claude Code · Codex · Pi · Copilot · Grok Build · Cursor

Define coding-agent assets once. Build the target-specific trees each agent expects.

Why this exists

SKILL.md is useful common ground, but it does not define a shared metadata format, plugin/package layout, or a common way to ship agents, hooks, and scripts. Each coding agent adds its own conventions. The same instructions also do not work equally well across models: wording that helps an OpenAI model may need a different version for an Anthropic model, and vice versa.

Maintaining copied skills and plugin files for every target is tedious. Copies drift. Small target or model differences become manual release work.

Agent Bundler keeps one source of truth, then lets you customize the parts that actually need to differ: frontmatter, Markdown sections, support files, and short target-wide preambles. It renders the result into the directory layout expected by Claude Code, Codex, Pi, GitHub Copilot, Grok Build, and Cursor.

canonical source + manifest
          │
          ▼
   import → customize → render
          │
          ├── Claude Code   .claude/skills/…
          ├── Codex         .codex-plugin/ + skills/…
          ├── Pi            .pi/skills/…
          ├── Copilot       plugin.json + skills/…
          ├── Grok Build    .grok/{skills,resources}/…
          └── Cursor       .cursor-plugin/ + skills/ + agents/…

Current scope

Today the target renderers produce skills, portable package resources, and selected native agent forms. Package profiles emit installable Claude, Codex, Pi, GitHub Copilot, and Cursor roots; one package keeps its historical flat root, while multiple packages are self-contained below package-ID roots. Grok emits a project skill/resource tree and accepts the Claude-compatible package format. Hooks, scripts, and target-native resources are not rendered by the current adapters. Unsupported capabilities fail instead of being silently discarded.

Agent Bundler is a compiler, not an agent runtime, installer, marketplace, or publisher. It creates target-ready files; your project or release workflow decides where to install or publish them. Run repository-owned vendor smoke tests before publishing; see Targets and CLI.

Install

Homebrew is the default install:

brew install alexei-led/tap/agentbundler

Or install with Go 1.26+:

go install github.com/alexei-led/agentbundler/cmd/agbun@latest

Start with an existing bundle

Discover the installed CLI, then build from a directory containing agentbundle.json:

agbun --version
agbun --help
agbun check
agbun build

Use agbun help build, agbun help check, and agbun help targets for the full command, safety, and target-ID reference.

build replaces the configured output directory. Use a dedicated generated directory, not a working project root. For a complete first bundle, see the quick start.

What can be customized

A target overlay can:

• merge or remove JSON frontmatter keys, including target-defined metadata such as tools;
• replace the whole Markdown body;
• replace the body under an exact heading path;
• add, replace, or delete support files;
• prepend a short target-wide policy through composition.

See customization for the exact sidecar format and examples.

Documentation

• Docs index
• User guide: how to think about Agent Bundler
• Install
• Quick start
• Configuration and source formats
• Target customization
• Targets and CLI reference
• Troubleshooting
• Architecture
• Agent Bundler Agent Skill

License

MIT

Documentation

Overview

Package agentbundler is the target-neutral Agent Bundler compiler product.

The executable entry point is cmd/agbun. Internal packages own source import, composition, target rendering, and generated-output effects.