AI agents
Catalog and project setup
The Catalog is a searchable list of 3,802 ready-made components for AI coding tools: agents, commands, skills, MCP servers, hooks, settings, status lines and plugins, gathered from public open-source collections. You add what you want to a stack, choose the project and the tools, and OmniGet shows the exact install plan before it writes anything.
Where it is
LLM › Catalog. The second row has Catalog, Installed and Project setup.
Browse the catalog
The index ships with the app, so you can search it offline. The files of a component are fetched from its source at a fixed version only when you install it.
- Tabs by kind: All, Agents, Commands, Skills, MCP, Hooks, Settings, Statuslines, Loops, Workflows, Plugins, Templates and Mods.
- Filters for category, license, the tool a component was written for, source, the tools it works in, marketplace and sort order.
- The MCP tab can also query the live MCP Registry.
- Add source adds a collection of your own.
Install components
- Find a component and click Install (or Add to stack to collect several first).
- In the Stack panel, set Where (the project folder) and Scope.
- Under Tools, pick the coding tools to install into. Detected selects the ones the project already uses.
- Choose what happens If a name is already taken: Install under another name, Keep theirs, skip mine or Replace theirs (backup kept).
- Click See plan to read the Install plan, including the commands the tools will run, then Install.
| Scope | Where it is written |
|---|---|
| Project | Inside the project folder, shared with whoever clones it. |
| Local | Inside the project, but only on this machine (files the tools keep out of git). |
| Global | In your user folder: every project on this machine gets it. |
OmniGet can install into 34 coding tools. In the Tools list, β marks an adapter not yet verified on your machine.
A stack can be kept with Save as collection or Export .omnistack. Same thing from the terminal shows the matching omniget agentkit command (Command line).
Installed
Installed lists what OmniGet installed in each tool and project, and what changed since. Group it by tool or by project. For each item you can update, reinstall, uninstall (or uninstall and keep your edits), restore, and see its history.
Already in your tools shows components that were there before OmniGet; Look opens one and Copy to… copies it into another tool.
Project setup
The project wizard sets up a project for your coding tools in a few steps:
- Project: pick a folder and click Detect.
- What was found: the languages, frameworks and commands found, the agent files already there, and templates you can turn on.
- What to install:
AGENTS.mdand guidance, commands, agents, settings, hooks and MCP servers. You can edit theAGENTS.mdtext; OmniGet writes it as a marked block, so your own text stays. - Tools: pick the coding tools, then See plan to open the Install plan and install.
- Review: after installing, Review the setup with an agent starts a read-only task with Omni to check the result.
Common problems
Workflows is empty
The bundled index has no workflow in this release.
“Choose the project folder.” or “Choose at least one tool.”
The stack needs a folder in Where and at least one tool in Tools before it can build a plan.
I want to undo an install
Open Installed and uninstall the item, or use Undo in the install plan right after installing.