by infragate
One capabilities.yaml wires skills, tools, rules, sub-agents, MCP servers, and plugins into Cursor, Claude Code, Codex, Windsurf, GitHub Copilot, and 30+ other AI coding agents
# Add to your Claude Code skills
git clone https://github.com/infragate/capaLast scanned: 6/11/2026
{
"issues": [
{
"file": "README.md",
"line": 84,
"type": "dangerous-command",
"message": "Dangerous command (pipe remote script to shell): \"curl -LsSf https://capa.infragate.ai/install.sh | sh\"",
"severity": "low"
}
],
"status": "PASSED",
"scannedAt": "2026-06-11T08:47:49.001Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}capa is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by infragate. One capabilities.yaml wires skills, tools, rules, sub-agents, MCP servers, and plugins into Cursor, Claude Code, Codex, Windsurf, GitHub Copilot, and 30+ other AI coding agents. It has 699 GitHub stars.
Yes. capa passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/infragate/capa" and add it to your Claude Code skills directory (see the Installation section above).
capa is primarily written in TypeScript. It is open-source under infragate on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh capa against similar tools.
No comments yet. Be the first to share your thoughts!
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.
https://github.com/user-attachments/assets/98442d19-44c9-43e6-b2c2-88156b189d5e
AI coding agents need rules, tools, and conventions — and right now those live scattered across CLAUDE.md, .cursor/rules/, AGENTS.md, MCP configs, and a half-finished internal doc. No two setups match.
CAPA collapses it into one capabilities.yaml next to your code: skills, tools, rules, sub-agents, plugins. capa install fans it out to every provider in its native format — .cursor/rules/ for Cursor, .claude/agents/ and CLAUDE.md for Claude Code, AGENTS.md for Codex, and so on. Capa-managed marker blocks keep your hand-written content untouched.
One file, version controlled, pinned by capabilities.lock, cached by SHA. The teammate who clones tomorrow gets the exact bytes you got today.
capabilities.yaml manages the content for your agent. Write rules, hooks, and tools once — capa runs them natively, supporting 35+ agents (Cursor, Claude Code, Codex, Windsurf, Copilot, Gemini CLI, and more). No more keeping .cursor/rules/, .claude/settings.json, and AGENTS.md in sync by hand.macOS and Linux:
curl -LsSf https://capa.infragate.ai/install.sh | sh
Windows:
powershell -ExecutionPolicy ByPass -c "irm https://capa.infragate.ai/install.ps1 | iex"
cd your-project
capa init
This creates a capabilities.yaml next to your code.
capa install
If you are already working on a project, and would like to get all of it's capabilities be managed by CAPA, simply use the /bootstrap skill. The agent will scan your project for skills, MCPs, relevant tools, hooks, and rules.
capa install resolves SHAs and downloads anything that isn't already in the cache. It then writes the per-provider files (.cursor/rules/, .claude/agents/, AGENTS.md, and so on) and registers one MCP endpoint with each agent on your list. The resolved SHAs land in capabilities.lock so the next clone gets the same bytes.
capa shcapa sh # list every configured tool
capa sh brave # list brave subcommands
capa sh brave search --query "…" # run a tool directly
Every tool you define is also a CLI command under capa sh. MCP tools live at capa sh <server> <tool>. Shell tools live at the top level (or under whatever group you assigned).
Guides, the full schema reference, and the registry catalog:
MIT