oh-my-agent weekly downloads statistics

oh-my-agent: A Specialist Team for the Coding Agent You Already Use

한국어 | 中文 | Português | 日本語 | Français | Español | Nederlands | Polski | Русский | Deutsch | Tiếng Việt | ภาษาไทย

oh-my-agent (oma) adds a team of specialists to the coding agent you already use: Claude Code, Codex CLI, Cursor, and 11 more. A planner breaks the work down, engineers build in parallel, a reviewer checks the result, and a debugger fixes root causes. It also does cited research, slide decks, videos and images. Most steps leave a file you can open, and in the long-running workflows a gate can send the agent back to work until your own test, lint or typecheck script passes.

Run this from your project root:

Then run oma doctor and type /plan add user accounts with a settings page in your agent. Your first 5 minutes walks through it.

Watch the full video (35s)

What you get

Workflows are what you type (or just say). They call in roles, the specialists. Skills are the know-how: each role carries its own, and your agent loads the rest whenever a task needs them.

| | What it gives you | Try it |

| 12 specialist roles | PM, architect, backend, frontend, mobile, database and infra engineers, QA reviewer, debugger, refactorer, docs curator, researcher (meet them) | /orchestrate build a TODO app with login | | 21 workflows | Slash commands from /brainstorm and /plan to /review, /debug and /scm. Most also start from a plain request (keyword banks in up to 11 languages) | "review this PR" | | 33 skills | Domain know-how that loads only when a task needs it: UI, APIs, schemas, Terraform, CI, security, git, observability | loads by itself, e.g. "add a Terraform S3 bucket" | | Files you can open | Plans, design docs, API contracts, ADRs, bug notes, per-agent results, security evidence, HTML explainers, recaps | ls .agents/results | | Checks that don't take the agent's word | In a long-running workflow, your own test, lint or typecheck script must pass before the agent may stop; oma ralph verify checks that a /ralph run left its plan, QA and refactor files | /ultrawork …, then oma goal set --gate test | | Research and content | Cited search, market research, papers, slide decks, MP4 videos, images, local voice, PDF/HWP to Markdown | /video, /convert | | One folder, 14 runtimes | One portable .agents/ directory, written into each runtime's own config files | oma link cursor |

Install · First 5 minutes · The team · Which workflow? · Everything in the box · Works with · Verification · FAQ · Docs

Install

The script installs bun if it is missing, installs the oma command globally (bun install --global oh-my-agent, skipped when oma is already on your PATH), then starts the interactive setup. The global command matters: the hooks (keyword detection, the Stop gate) and several workflows call oma, and the hooks silently do nothing when they cannot find it. If you skip the script, install it yourself with bun install --global oh-my-agent (npm install --global oh-my-agent or brew install oh-my-agent also work).

Windows, or without the install script

On Windows the installer hides Antigravity, Hermes, and Kimi, and the hook wrapper is a bash script. The default Aside browser MCP installs through bash, so deselect it if you have no bash.

The setup asks for your response language, which agent runtimes to wire up, capability providers, a browser MCP, a model preset, and a skill preset. Pick All for the skill preset if you are unsure: workflows are always installed, and several of them (/orchestrate, /work, /ultrawork, /ralph, /docs, /security) need skills that only All includes.

What the installer also does by default…

Description from the npm listing.