Capa

Agentic Capabilities and Package Manager

CAPA is the package manager for AI coding agents. Declare your skills, tools, rules, sub-agents, MCP servers, and plugins once in capabilities.yaml, run capa install, and CAPA writes them into Cursor, Claude Code, Codex, Windsurf, GitHub Copilot, and 35+ other agents.

Why CAPA?

An AI coding agent needs to know when to act and to have the tools to act with. Wiring that up usually means scattering config across half a dozen files: MCP servers in one place, skill markdown in another, team conventions in CLAUDE.md, Cursor rules in .cursor/rules/, a half-finished onboarding doc somewhere in Notion. Nobody's setup matches anyone else's.

CAPA collapses that into one capabilities.yaml next to your code. You list your skills (markdown that tells the agent how to do something), the tools each skill needs (MCP calls and shell commands), your rules, your sub-agents, and any plugins you want pulled in. capa install does the rest. Cursor gets .cursor/rules/. Claude Code gets .claude/agents/ and CLAUDE.md. Codex gets AGENTS.md. Each provider on your list gets the files it expects, with capa-managed marker blocks for the parts it owns.

One file, version controlled, pinned by capabilities.lock, cached by SHA. The teammate who clones tomorrow gets the same bytes you got today.

Screenshots

CAPA is equipped with local web UI. You can visualize your capabilities.yaml, browse registries, manage credentials, and see exactly what each agent will receive.

The project view shows installed plugins, configured providers, and your full capability inventory. The bar across the top tracks token savings from on-demand tool exposure: the agent sees only the tools it's actively using, and pulls any of the rest in by name when it needs them.

Scrolling down the same page brings up sub-agents, rules, project options, and credentials. Every entry carries an INLINE / GITHUB / REMOTE badge so you can see at a glance where each one came from.

The Registries tab pulls skills and plugins from external catalogs. Need a private one? Run capa registry add owner/repo@my-adapter (or use the Manage registries page). capa fetches the adapter from GitHub, GitLab, or an HTTPS URL, validates it, and it shows up here to

... View full README on GitHub