Modules are the powers
Layer 03. What the agent can do and what it can reach. Skills, MCP tools, and the packs that switch on with a credential.
A skill is a workflow the agent runs when you invoke it: a briefing, a release, a worktree, a plan. A tool is something it can reach: a pull request, a database, a browser, a search. Packs group the tools that need a credential and stay dormant until one is added. All of it ships in the open-source plugin; the catalog on the site shows the same set grouped by what it does.
Four groups
The catalog is grouped by what a capability is for. Each page lists every skill and tool in the group with how to invoke it, and links to the deeper pages.
Plan and run
Projects and tasks, roadmap, the goals ladder, briefings, the session radar.
Build and ship
Worktrees, pull-request review, API collections, deploy checks, releases.
Reach and see
Browser, logs, database, search, chat, support desk, SEO.
Brain and memory
Capture, compile, self-review, sync, dashboard, seed bundles.
Packs
| Pack | Needs | Unlocks |
|---|---|---|
| SEO | Google OAuth, optional SerpAPI and OpenPageRank keys | Search Console, PageSpeed, SERP data, domain rank, WordPress content |
| Browser | nothing beyond the install | screenshots, PDFs, page-to-Markdown, recordings, scripted flows |
| Database | a connection string | read-only queries and schema against a replica or a fork |
| GitHub | a token | pull requests, checks, run logs, issues, fast-forwards, the review skill |
| API | nothing | request collections drafted as files for your own client |
External accounts and what they cost are on Accounts.
Industry modules
An industry module is the same powers tuned to one sector: the packs it needs, the skills its workflows call for, and the regulatory knowledge that sector requires, deployed per customer on the same brain and the same agent. They are described on the site rather than here; the open plugin is the horizontal layer they build on.