zom · the ZomHub command line
Install the CLI
One command pulls a bundle from the registry into your project, laid out for the agent tool you use. It needs Node.js 18 or newer and nothing else.
Install once
Or with the package manager you already use:
Or run it without installing
npx downloads the CLI on first use and runs it. Every command works the same with npx zomhub in front instead of zom.
First run
The first clone asks which tool you use and remembers it. Files land where that tool reads them:
- --tool claude-codeClaude Code
- --tool cursorCursor
- --tool codexCodex
- --tool gemini-cliGemini CLI
- --tool copilotGitHub Copilot
Pass --tool to override, or --tool neutral for the plain layout. Then open the folder in your tool, fill in .env from .env.example, and run.
Commands
- zom search <query>
- Search the registry from the terminal.
- zom info <owner>/<slug>
- What a bundle contains: agents, env, files, versions.
- zom clone <owner>/<workflow> [dir]
- Pull a workflow into a folder, laid out for your tool.
- zom add <owner>/<agent>
- Add an agent to the project you are in.
- zom update [owner/slug]
- Bring what you added or cloned here up to the latest version. Your edits are kept.
- zom config [--tool name]
- Show or change the default tool and the API URL.
zom help shows the same list in the terminal. The CLI only pulls: it never asks you to sign in, and it never uploads anything.
Keeping up to date
Every clone and add writes .zomhub/installed.json next to the files. Run zom update in that folder to pull the latest version of each bundle. Files you edited stay as they are and are listed; --force overwrites them.
Publishing your own
Publishing happens on the site, not in the CLI. The publish page takes an upload, or a public GitHub repository whose agents/ folder holds your agents.
No Node.js?
Every bundle page has a curl tab that downloads the archive for your tool with no CLI at all: