Agents Pack gives Claude Code, Codex, and Cursor a shared set of project instructions, skills, and subagents. You choose the agents and components you want once; Agents Pack renders the right files for each provider and keeps track of what it owns.
New here? Start with the Agents Pack user guide.
Agents Pack supports macOS and Linux on ARM64 and x64. The installer downloads
one standalone executable, verifies its SHA-256 checksum, and places it under
~/.local/bin without sudo:
curl -fsSL https://farfarawaylabs.github.io/agentspackai/install.sh | shThen verify the command:
agents-pack --versionIf ~/.local/bin is not already on your PATH, the installer prints the exact
line to add. See the installation guide
for custom directories, exact-version installation, upgrades, and source
development.
Coding agents become much more useful after you teach them how you work. The problem is that each agent expects its instructions, skills, and subagents in different places and formats.
Agents Pack keeps one maintained content pack and adapts it for:
- Claude Code;
- Codex; and
- Cursor.
It also lets you create repository-specific or user-wide skills and subagents once, then synchronize them across every selected agent.
- Repository-wide or global installation.
- Standalone macOS and Linux executables with a checksum-verifying installer.
- Interactive selection of agents and components.
- One core instruction set, 24 portable skills, and six native subagents.
- Provider-specific rendering for Claude Code, Codex, and Cursor.
- Safe component installation and removal after initialization.
- Canonical user-owned skills and subagents.
- Forking an official skill or subagent into user ownership.
- Read-only status, drift detection, dry runs, and transactional writes.
- Official pack release notes and update checks.
- Version pinning, local rollback, and safe ejection.
- A static registry and GitHub Release workflow for official pack delivery.
Global scope currently supports Claude Code and Codex. Global Cursor instructions are not supported yet; Cursor can be selected in repository scope.
Agents Pack separates content into two groups:
| Content | Editable source | Updated by |
|---|---|---|
Official ap- components |
The installed core pack | update, install, and remove |
| User-owned components | .agents-pack/user/ or ~/.agents-pack/user/ |
You, followed by agents-pack sync |
Generated provider files are not the editable source. Agents Pack records their hashes and refuses to overwrite unexpected edits, missing files, malformed managed blocks, or path conflicts.
Move into the project you want to configure, then start the interactive setup:
cd /path/to/your-project
agents-pack initUse the arrow keys to move through each menu. Press Space to toggle agents or components, and Enter to confirm the visible selection. Repository scope, all compatible agents, and the recommended component set are selected by default.
Or initialize non-interactively:
agents-pack init \
--scope repository \
--agents all \
--components recommended \
--yesWithout --pack, Agents Pack downloads the current official content pack.
| Command | Purpose |
|---|---|
agents-pack init |
Initialize repository or global scope |
agents-pack status |
Inspect the installation and detect drift |
agents-pack list |
List installed or available components |
agents-pack install <id> |
Install an available official component |
agents-pack remove <id> |
Remove an optional official component |
agents-pack create skill <name> |
Create a canonical user-owned skill |
agents-pack create subagent <name> |
Create a canonical user-owned subagent |
agents-pack fork <id> --name <name> |
Copy an official skill or subagent into user ownership |
agents-pack sync |
Regenerate provider copies from user-owned source |
agents-pack update --check |
Check the official registry without writing |
agents-pack update |
Preview or apply a content-pack update |
agents-pack pin |
Keep the currently installed pack version |
agents-pack unpin |
Allow forward updates again |
agents-pack rollback [version] |
Restore an older pack from the local cache |
agents-pack eject |
Safely remove managed outputs |
Run agents-pack <command> --help for the exact options. When running from
source, replace agents-pack with:
bun /path/to/agentspackai/src/cli/main.ts
The editable first-party content lives under
content/packs/core/. The
content catalog describes the included instructions,
skills, and subagents.
Repository installations keep readable state under .agents-pack/. Global
installations use ~/.agents-pack/. Generated Claude, Codex, and Cursor files
remain in their native provider directories.
Agents Pack stores the exact installed pack in a user-level, content-addressed cache. This lets component operations and rollback work without the original source directory.
The project currently uses Bun and TypeScript:
bun install
bun run check
bun run cli --help
bun run cli:buildBuild the current official pack artifact locally with:
bun run pack:buildThe release process and one-time GitHub setup are documented in Agents Pack content distribution. Standalone CLI releases and the installer are documented in Agents Pack CLI distribution.
- Complete user guide
- Skill catalog
- Core content catalog
- User-owned components
- Updates, pinning, and rollback