Install Routes¶

Four ways to get packs into your agent. Pick the one that matches your workflow.

Route 1: agentbundle CLI (recommended)¶

The standard route. Installs into the current repo (repo scope) or your home directory (user scope).

pip install agentbundle
agentbundle install --pack core

Key commands¶

# See all available packs
agentbundle list-packs

# See what you have installed
agentbundle list-installed

# Install at user scope (follows you across every project)
agentbundle install --pack desk-research --scope user

# Install a profile (curated pack bundle)
agentbundle install --profile solution-architect

# Preview before writing any files
agentbundle install --pack core --dry-run

# Upgrade to the latest version
agentbundle upgrade --pack core

# Target a specific agent adapter
agentbundle install --pack core --adapter cursor
agentbundle config set adapter cursor  # set once, apply everywhere

Adapters¶

Auto-detects your agent. Override with --adapter:

Adapter flag	Agent
`claude-code`	Claude Code (default fallback)
`codex`	OpenAI Codex
`cursor`	Cursor
`copilot`	GitHub Copilot
`gemini`	Gemini CLI
`kiro-ide`	Kiro IDE
`kiro-cli`	Kiro CLI

Route 2: Claude Plugins¶

Install directly from Claude's plugin marketplace without touching the CLI.

First, add the marketplace (one-time setup):

claude plugin marketplace add eugenelim/agent-ready-repo

Then install any pack using <pack>@agent-ready-repo:

claude plugin install core@agent-ready-repo
claude plugin install desk-research@agent-ready-repo

Available for all 14 packs. Pack names match the directory names under packs/.

Route 3: APM (Agent Package Manager)¶

For teams using APM as their primary package manager:

apm install eugenelim/core
apm install eugenelim/desk-research --scope user

Route 4: Local clone¶

For catalogue contributors or teams building their own fork:

git clone https://github.com/eugenelim/agent-ready-repo
cd agent-ready-repo
pip install -e packages/agentbundle
agentbundle install --pack core

With an editable install, agentbundle defaults to the local clone as its catalogue source — so list-packs shows local state and installs come from your working tree.

Scopes¶

Every pack has a natural install scope:

Scope	Where it lands	When to use
`repo`	`.claude/skills/`, `.codex/`, etc. in the current repo	Skills specific to this project
`user`	`~/.claude/skills/`, etc. in your home dir	Skills that follow you across all repos

The pack's README documents which scope it defaults to. Override with --scope user or --scope repo.

File safety¶

Installs never silently overwrite your edits. If a file you've modified would be overwritten, it lands as <name>.upstream instead — a companion file you merge at your own pace. Your edits are always preserved.

→ File safety contract explained