Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add infragate/capa --skill capabilities-managergit clone --depth 1 https://github.com/infragate/capaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/infragate/capa/capabilities-manager)<a href="https://agentmods.dev/skills/infragate/capa/capabilities-manager"><img src="https://agentmods.dev/badge/skills/infragate/capa/capabilities-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/infragate/capa/capabilities-manager"><img src="https://agentmods.dev/badge/skills/infragate/capa/capabilities-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00270 | $0.02590 |
| Opus 5.5 | $0.00108 | $0.01036 |
| Sonnet 5.5 | $0.00054 | $0.00518 |
| Haiku 4.5 | $0.00027 | $0.00259 |
Grade A, and why
capabilities-manager scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capabilities Manager
The capa CLI keeps a single source-of-truth file — capabilities.yaml (or .json) — that describes everything an agent can do in this project: skills, MCP servers, tools, hooks, sub-agents, rules, plugins, and per-provider files (AGENTS.md, CLAUDE.md). Editing that file and running the right capa command is the whole loop.
This skill is the routing layer for that loop. The actual command reference, schema, full YAML examples, and troubleshooting tables live in references/. Load the one you need rather than re-deriving its contents — they are kept up to date and are the authoritative source.
How capa works (one screen)
- The file is the source of truth.
capabilities.yamldeclares what gets installed. Capa never auto-discovers anything from.claude/,.cursor/, etc. — if it's not in the file, capa won't manage it. (Onboarding an already-configured project is thebootstrapskill's job.) capa installwrites everything. Skill directories under each provider, MCP client config (.mcp.json,.cursor/mcp.json, etc.),AGENTS.md/CLAUDE.mdblocks, hook entries, rules — all rewritten from the file. Anything labeledname: capa:<id>is capa's; entries the user authored by hand are left alone. Plugins unpack into the same primitives (skills, servers, rules, sub-agents, hooks).capa cleanremoves only what capa wrote. Safe to run; doesn't touch user-authored files or settings entries. Passthrough writes (capa add --passthrough/capa install --passthrough) are not managed —capa cleanwill not remove them.- A background server at
localhost:5912handles credential prompts, tool execution (capa sh), MCP endpoints, the Web UI capabilities editor, registries, and the Activity feed. Started bycapa init/capa install; lifecycle iscapa start | stop | restart | status. - Secrets are
${VarName}placeholders anywhere in the file. Capa prompts for them via web UI on install, or loads from.envwithcapa install -e. capa wrap <provider>runs the agent from a shadow workspace under~/.capa/workspaces/so provider dirs never pollute the real repo. Mutating commands refuse to run inside a wrap workspace — always edit/install from the real project path.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +1 lines a0089a78eb58
- 1mo ago First seen · 100 lines · 270 tokens per session scan A 969daa06c4be
capabilities-manager is a skill published in the GitHub repository infragate/capa (719 stars, last pushed yesterday), licensed MIT. It adds 270 tokens to every session and 2,590 once invoked, about $0.0011 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
frontmcp-development
Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents…
pipefy-ai-agents
Use this skill when the user wants to create, read, update, delete, or troubleshoot AI agents (conversational agents with behaviors). Includes pre-flight validation and pipe-scoped knowledge bases (list, plain text/document/data lookup CRUD, access probe) attached via dataSourceIds. For traditional automations and AI…
pipefy-api-fallback
Use this skill when a toolkit operation fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow…
git-cheatsheet
Use this skill when working with git commands, version control, or repository management.
pipefy-members-email-webhooks
Use this skill when the user wants to manage pipe membership, send or read card inbox emails, use email templates, or manage webhooks.
reskill-usage
Teaches AI agents how to use reskill — a Git-based package manager for AI agent skills. Covers CLI commands, install formats, configuration, publishing, and common workflows.