zom — install AI agents and workflows into Claude Code, Cursor, Codex, Gemini CLI and Copilot

zom is the command line for ZomHub, the registry for AI agents and workflows. One command pulls a bundle (subagents, skills, commands, AGENTS.md, MCP config, .env.example) into your project, laid out for the tool you use:

| Tool | Where the files land | | --- | --- | | Claude Code | .claude/agents/*.md, .claude/commands/, .claude/skills/, CLAUDE.md, .mcp.json | | Cursor | .cursor/agents/, .cursor/commands/, .cursor/skills/, AGENTS.md, .cursor/mcp.json | | Codex | .codex/agents/*.toml, .codex/prompts/, .agents/skills/, AGENTS.md | | Gemini CLI | .gemini/agents/, .gemini/commands/*.toml, GEMINI.md, .gemini/settings.json | | GitHub Copilot | .github/agents/*.agent.md, .github/prompts/, .github/skills/, AGENTS.md, .vscode/mcp.json |

No copying .claude/agents folders by hand, no install scripts per repo, no account. Find the right agent or workflow at https://hub.zomler.com/explore, then:

npx zomhub add zomhub/test-writer        # add one agent to the project you are in
npx zomhub clone zomhub/pr-reviewer      # clone a whole workflow into a folder

Install

npm install -g zomhub      # gives you `zom` (and `zomhub` as an alias)
zom --version

Also pnpm add -g zomhub, yarn global add zomhub, bun add -g zomhub, or run any command with npx zomhub … and skip the install. Needs Node 18 or newer. Zero dependencies.

Quick start

zom search review                  # find bundles; prints a link to the same search on hub.zomler.com
zom info zomhub/pr-reviewer        # what is inside: agents, env vars, files, versions
zom clone zomhub/pr-reviewer       # download a workflow into ./pr-reviewer
zom add zomhub/test-writer         # merge an agent into the current project
zom update                         # later: bring everything installed here to the latest version

The first clone or add asks which tool you use and remembers it (zom config --tool cursor changes it). Then open the folder in your tool, copy .env.example to .env, and run.

What is a bundle

• An agent bundle is a subagent definition (a markdown file with name, description, model tier and capabilities in its frontmatter) plus the skills, commands, MCP config and env example it needs. ZomHub stores it tool-neutral and compiles it for your tool on download: Claude Code model: sonnet and tools: dialect, Codex TOML, Copilot .agent.md, and so on.
• A workflow bundle is an ordered set of published agents, each with optional appended instructions, plus the workflow's own files (WORKFLOW.md, commands, README, .env.example). Cloning materialises the whole tree.

Browse both kinds with README, file list, agent and env previews, stars and clone counts at https://hub.zomler.com/explore.

Commands

| Command | What it does | | --- | --- | | zom clone <owner/slug> [dir] [--version v] [--tool name] [--force] | Downloads every file into dir (default: the slug), laid out for the chosen tool. Refuses a non-empty directory unless --force. | | zom add <owner/slug> [--version v] [--tool name] [--force] | Writes the bundle's files into the current directory, keeping what is there. Existing files are skipped and listed unless --force. | | zom update [owner/slug ...] [--dir path] [--tool name] [--force] | Re-downloads the bundles recorded in .zomhub/installed.json and re-places their files. Files you edited are kept and listed; --force overwrites them. owner/[email protected] moves one bundle to that version. | | zom search <query> [--kind agent\|workflow] [--sort stars\|clones\|updated\|new] [--limit n] | Prints a table of matching bundles and a link to the same search on the site. | | zom info <owner/slug> | Name, description, kind, version, stars, clones, agents, env vars, and the clone command. | | zom config [--tool name] [--api url] [--web url] [--reset] | Shows the effective settings, or saves new ones to ~/.zom/config.json. |

zom --help, zom <command> --help and zom --version work as expected. owner/[email protected] is accepted anywhere a bundle reference is.

The CLI is pull-only: it never signs in and never uploads. Publish your own agents at https://hub.zomler.com/dashboard/publish, as an upload or straight from a public GitHub repository whose agents/ folder holds the definitions.

Choosing a tool

1. --tool <name> on the command: claude-code, cursor, codex, gemini-cli, copilot, or neutral (the stored layout).
2. The ZOM_TOOL environment variable.
3. tool in ~/.zom/config.json, set with zom config --tool <name> or by answering the prompt.
4. At a terminal with nothing set, zom asks once and offers to save the answer. In CI or a pipe it uses neutral and prints a hint.

After writing, clone, add and update print Placed for <tool>: N files.

Updating without losing your edits

Clone and add write .zomhub/installed.json next to the files: which bundles, at which version, for which tool, and a hash of every file as placed. zom update compares each file on disk with that hash. Unchanged files are replaced, edited files are kept and listed, and files the new version dropped are removed only when unchanged. Commit the record with your project so teammates can run zom update too.

Configuration

| Setting | Order of precedence | | --- | --- | | API base | ZOM_API env, then api in ~/.zom/config.json, then https://zomhubapi.zomler.com | | Web base (for printed links) | ZOM_WEB env, then web in ~/.zom/config.json, then https://hub.zomler.com | | Tool | --tool flag, then ZOM_TOOL env, then tool in ~/.zom/config.json, then a prompt (or neutral when not at a terminal) |

For a local registry: export ZOM_API=http://127.0.0.1:8010.

Errors

Every failure exits non-zero with one line on stderr: Not found: owner/slug for an unknown bundle, the API's message otherwise. Usage mistakes exit with code 2.

Development

npm run check                                        # node --check on every file
ZOM_API=http://127.0.0.1:8010 API_TOKEN=dev-local-token npm test   # test/smoke.sh against a running API

The smoke test publishes a fixture through the API (the CLI itself cannot), then runs search, info, clone, add, update (up to date, new version keeping an edited file, --force, pinning back, removal of dropped files) and the error mapping, and deletes what it created.

Layout: bin/zom.js is the entry point, src/cli.js parses arguments and dispatches, src/api.js talks to the API, src/config.js reads env and ~/.zom/config.json, src/files.js writes files safely and keeps the install record, src/tool.js resolves the target tool, and src/commands/*.js hold one command each.

Related searches this answers

How to install Claude Code subagents · add agents to .claude/agents · Cursor agents and rules · Codex AGENTS.md and .agents/skills · Gemini CLI agents · GitHub Copilot custom agents · SKILL.md skills · MCP config per tool · AI agent workflows · agent registry and marketplace.