Quiver Cli

quiver-cli

Compose a selected subset of skills, slash commands, provider plugins and MCP servers from a central catalog into any repo — as **native configs** for opencode, Claude Code and Codex — with **lockfile-based drift awareness**.

One thing done right: repo composition + drift detection. No marketplace, no extra agents, no command abstraction.

• One source of truth — .agents/ + quiver.lock, committed to the repo.
• Native output — .opencode/, opencode.json, .claude/, .mcp.json, .codex/ are generated and gitignored; each tool loads its own format.
• Drift detection — content digests for skills/commands, tool snapshots for MCP servers (including tool-description poisoning).
• Upstream awareness — know when a source repo updates a skill you imported.

Quick start

Requires **Node >= 20.12** (the interactive pickers depend on it; `init`, `add`, `remove` and `providers` abort on older versions).

From the root of the target repository:

pnpm dlx quiver-cli init

The interactive picker lets you select skills, commands and MCP servers from the catalog; quiver then materializes them into `.agents/`, writes `quiver.lock`, generates the native provider configs and patches `.gitignore`.

git add .agents quiver.lock .gitignore
git commit -m "chore: add agent config"

Restart your AI tool (opencode, Claude Code, Codex) to load the configs. Day to day:

quiver-cli add mcp:context7   # add one entry (skill:/command:/mcp:/plugin:)
quiver-cli sync               # regenerate provider configs from .agents/
quiver-cli check              # detect drift (CI-friendly: --json, exit 1)

Commands

Command	Description
quiver-cli init	Interactive picker; write native configs + quiver.lock
`quiver-cli add