Skip to content
/
Phase D Batch 15

Phase D Batch 15 — "oh-my-*" Naming-Pattern Family

Phase D Batch 15 — "oh-my-*" Naming-Pattern Family

Batch theme: Multi-agent frameworks using the "oh-my-*" naming convention, beyond the 3 oh-my-codex variants analyzed in Phase B Batch 23.

Roster (10)

slug stars distribution cli_binary local_ui orchestration multi_model tier
stefandevo-oh-my-claude 7 claude-plugin no none hierarchical no A
zephyrpersonal-oh-my-claude 0 claude-plugin no none hierarchical yes (x-omo-cost routing) A
techdufus-oh-my-claude 147 claude-plugin no none hierarchical no A
ssenart-oh-my-claude 14 bash-script-bundle no terminal status line none no A
opensoft-oh-my-opencode 544 claude-plugin yes (TypeScript) none hierarchical yes (multi-provider) A
oh-my-claudecode-mazen 5 claude-plugin no none unknown no C
baekenough-oh-my-customcodex 3 npm-package yes (omcustomcodex) none hierarchical yes (reasoning-sandwich) A
lukasdias-oh-my-agent-skills 1 cli-tool (Rust/cargo) yes (oh-my-agent-skills) terminal TUI none no A
huangdijia-cc-plugins 10 claude-plugin no none sequential no A
oh-my-claudecode-yeachan 34,919 npm-package yes (omc) none hierarchical yes (opus/sonnet/haiku tiers) A

What Each "oh-my-*" Customizes — Side-by-Side Table

The central question for this batch: what does each author mean when they use the "oh-my-*" prefix?

Framework Primary Object Customized "oh-my-X" Meaning Parent Tradition
oh-my-claudecode (Yeachan) Full Claude Code workflow lifecycle "The complete orchestration platform for Claude Code — don't learn it, just use OMC" oh-my-opencode (direct port/extension)
oh-my-opencode (opensoft) OpenCode CLI agent workflow "Multi-agent orchestration runtime for OpenCode, as oh-my-zsh is to zsh" oh-my-zsh (naming origin); original of this cluster
oh-my-claude (TechDufus) Pre-execution quality gate chain "A behavioral framework that installs discipline (advisor→critic→risk-assessor) before any code runs" oh-my-opencode (forked Sisyphus from stefandevo)
oh-my-claude (stefandevo) Agent role hierarchy "Sisyphus/Prometheus/Momus orchestration patterns ported to Claude Code" oh-my-opencode (explicit port)
oh-my-claude-code (zephyrpersonal) Agent cost routing metadata "Agents with x-omo-cost routing tags (FREE/CHEAP/EXPENSIVE) replacing manual model selection" oh-my-opencode (independent reimplementation)
oh-my-customcodex (baekenough) Codex agent catalog (compilation metaphor) "Agents are compiled from skills; sauron-mgr is the compiler; 49 agents, 123 skills" oh-my-codex-yeachan (Codex port) + oh-my-claudecode-yeachan (adds Claude CC bridge)
oh-my-claude (ssenart) Terminal prompt status line "oh-my-posh integration showing Claude API usage, token counts, and Pro tier remaining" oh-my-posh (shell prompt theming — NOT orchestration tradition)
oh-my-agent-skills (lukasdias) Skill file discovery/browsing "A Rust TUI to browse and copy agent skill files to clipboard" oh-my-zsh (name only) — does not install into any agent tool
oh-my-claude-code-plugins (huangdijia) Multi-plugin marketplace "5 separately installable plugins: subagents, git, git-flow, mcp, skills" oh-my-zsh plugin architecture metaphor
oh-my-claudecode (mazenyassergithub) Unknown (Tier C) Insufficient evidence; README is SEO-generated; suspected derivative of yeachan oh-my-claudecode-yeachan (claimed derivative)

Cross-Batch Comparison: oh-my-codex (Batch 23) vs oh-my-claudecode/claude (Batch 15)

Dimension oh-my-codex-yeachan (B23) oh-my-claudecode-yeachan (B15) Relationship
GitHub stars 29,662 34,919 Claude version has ~18% more stars
Target tool Codex CLI Claude Code Same author, parallel products
CLI binary omx omc Symmetric naming
Skill count 46+ 28+ skills Codex version has more skills
Persona/agent count 20+ 19 Comparable
Deep interview YES — quantitative (0.15/0.20/0.30 thresholds) YES — mathematical ambiguity scoring + Socratic gate Both; Claude version adds hard execution gate
Team mode YES — tmux multi-session YES — omc team N:codex/gemini/claude Claude version supports mixed-CLI workers (Codex+Gemini)
Ultrawork keyword YES YES (ultrawork/ultraqa) Inherited pattern
State persistence .omx/ directory .omc/ directory + SQLite Claude version adds SQLite
Multi-model YES (claude-opus/sonnet/haiku) YES (opus/sonnet/haiku tiers) Symmetric
Ralplan consensus Not documented YES (planner→architect→critic) Claude version only
Autopilot 6-phase Partial (ultrawork phases) YES (explicit 6-phase lifecycle) Claude version only
Companion oh-my-claudecode (this batch) oh-my-codex (B23) Mutual companions
Dimension oh-my-codex-scalarian (B23) baekenough-oh-my-customcodex (B15)
Purpose v2 monorepo rebuild of oh-my-codex Codex port with Claude CC bridge
Status Archived (April 2026) Active (develop branch)
Stars 65 3
Innovation monorepo split "compilation" metaphor (skills=source, agents=compiled)
Multi-tool Codex only Codex+Claude Code
Dimension oh-my-codex-sigridjineth (B23) zephyrpersonal-oh-my-claude (B15)
Role Ambassador fork of oh-my-codex Independent reimplementation of oh-my-opencode for Claude Code
Routing mechanism Tier routing (Haiku/Sonnet/Opus by complexity) x-omo-cost metadata tags (FREE/CHEAP/EXPENSIVE)
Stars 14 0
Distinctive addition Notifications (Discord/Telegram), LSP/AST ULW parameter flags (--max-iterations, --thoroughness)

The Two Traditions Colliding

The "oh-my-*" prefix carries two completely distinct lineages:

Tradition 1: Orchestration lineage (oh-my-zsh → oh-my-opencode → oh-my-claudecode/oh-my-codex)

  • Meaning: "Zero-configuration enhancement layer for [tool]"
  • Characteristics: multi-agent orchestration, Sisyphus pattern, tmux workers, keyword detection hooks
  • Frameworks: opensoft, yeachan-claudecode, yeachan-codex (B23), stefandevo, zephyrpersonal, techdufus, baekenough

Tradition 2: Terminal customization lineage (oh-my-zsh → oh-my-posh → ssenart's oh-my-claude)

  • Meaning: "Shell theming / status display for [tool]"
  • Characteristics: status line display, API usage meters, oh-my-posh segments
  • Frameworks: ssenart-oh-my-claude (this batch)

Accidental convergence (neutral)

  • lukasdias-oh-my-agent-skills: Uses the name for a Rust TUI skill browser — not an agent tool at all
  • huangdijia-cc-plugins: Uses the oh-my-zsh plugin-marketplace metaphor for a separate purpose

This naming collision is taxonomically significant: the "oh-my-*" prefix has become a general-purpose "enhancement layer" signal, not specifically an orchestration signal.

Intra-Batch Patterns

Canonical descent concentration: 7 of the 9 resolvable frameworks trace directly to opensoft/oh-my-opencode as their semantic origin. opensoft is the canonical parent of the orchestration branch of this naming cluster. The genealogy flows: oh-my-zsh (naming tradition) → oh-my-opencode (2024, opensoft) → oh-my-claudecode/oh-my-codex (yeachan) → stefandevo/zephyrpersonal/TechDufus (Claude Code ports) → baekenough (Codex port of the Claude Code port). The naming meme propagated faster than the architecture — later adopters forked the pattern without fully reimplementing the underlying machinery.

Star concentration is extreme: oh-my-claudecode-yeachan (34,919) accounts for 98.9% of all stars in this batch. The remaining 9 frameworks sum to 385 stars. This reflects both first-mover advantage (the original Claude Code port of oh-my-opencode) and network effects from the Discord community and companion oh-my-codex project. The pattern repeats from Batch 23 where oh-my-codex-yeachan (29,662) dominated its cohort.

Model-routing independence: Three frameworks independently developed cost-aware model routing — zephyrpersonal (x-omo-cost tags: FREE/CHEAP/EXPENSIVE), yeachan (opus/sonnet/haiku tiers), baekenough (reasoning-sandwich: opus→sonnet→haiku). None of the 11 seeds has this pattern explicitly. This is convergent evolution observed across both Batch 15 and Batch 23 (sigridjineth's tier routing).

Keyword-detector divergence: All orchestration-tradition frameworks use UserPromptSubmit hooks to detect magic keywords (ultrawork, ulw, ralph, autopilot). But the keyword vocabulary diverged: yeachan uses ralph/autopilot/ultrawork/ultraqa, TechDufus uses ultrawork/ultraresearch/ultradebug, zephyrpersonal uses ulw. No standardization occurred despite common ancestry.

Non-orchestration masquerade: 3 of 10 frameworks named "oh-my-" are not orchestration frameworks: ssenart (terminal status line), lukasdias (Rust TUI skill browser), mazenyassergithub (Tier C, suspected auto-generated). The "oh-my-" name signals intent without guaranteeing orchestration architecture.

Most Interesting Finds

  1. opensoft/oh-my-opencode as canonical parent: The entire orchestration branch of the oh-my-* cluster — covering frameworks in both Batch 15 and Batch 23 — derives from opensoft's 2024 project. The dynamic Sisyphus prompt generation (buildDynamicSisyphusPrompt()) and Boulder state machine are the common architectural ancestors. Yet opensoft has only 544 stars while its derivatives collectively have 65,000+. opensoft also has a documented identity crisis: an impersonation site at ohmyopencode.com, and was cited by Anthropic when blocking OpenCode's Claude OAuth access in January 2026.

  2. The ssenart naming collision: ssenart/oh-my-claude is the most sharply different project in the entire batch — it is a terminal prompt theming tool using oh-my-posh segments to display Claude API usage meters. It shares no code, architecture, or intent with the orchestration cluster. The "oh-my-claude" name was chosen because ssenart was following the oh-my-posh theming tradition, not the oh-my-opencode orchestration tradition. This demonstrates the instability of the "oh-my-*" namespace as a taxonomy signal.

  3. baekenough's compilation metaphor: The claim that "agent systems are compiled, not configured" — with skills as source code, agents as compiled artifacts, and mgr-sauron as the compiler — is the most philosophically novel architectural framing in the batch. No other framework uses this metaphor. At 49 agents and 123 skills, baekenough has the largest agent catalog in the batch (excluding yeachan).

Items Written as Tier C

  • oh-my-claudecode-mazen (mazenyassergithub): README is SEO-style auto-generated content with suspicious ZIP download instructions. plugin.json contains only minimal metadata. Likely a derivative of oh-my-claudecode-yeachan with obfuscated install instructions for SEO purposes. Only 00-summary.md and METRICS.yaml written per Tier C escape rule.

Cross-References Discovered

  1. oh-my-claudecode-yeachan → oh-my-opencode: yeachan's README and METRICS acknowledge opensoft as the parent of the Sisyphus orchestration pattern. The Ouroboros project (ambiguity scoring) is credited as the origin of the deep-interview mathematical gating.

  2. baekenough → oh-my-claudecode-yeachan + oh-my-codex-yeachan: baekenough is explicitly a derivative of yeachan's Codex framework, adding Claude Code bridge. METRICS.yaml in baekenough notes: "Codex port of oh-my-claudecode-yeachan."

  3. mazenyassergithub → oh-my-claudecode-yeachan: Claimed derivative in yeachan's METRICS.yaml forks_or_derivatives field.

  4. oh-my-claudecode-yeachan + oh-my-codex-yeachan (B23) mutual companions: yeachan explicitly pairs oh-my-claudecode (Claude Code) with oh-my-codex (Codex CLI) as companion tools. Both batches analyze a yeachan framework; they are the two legs of a dual-CLI strategy.

  5. oh-my-codex-sigridjineth (B23) ↔ oh-my-claudecode-yeachan (B15): sigridjineth is the oh-my-codex "ambassador" that added Claude Code as its primary target. It implements keyword-detector and skill-injector hooks inherited from yeachan's oh-my-claudecode. These two frameworks share hook architecture.

  6. techdufus → stefandevo: TechDufus README references stefandevo as a prior port of oh-my-opencode Sisyphus to Claude Code; TechDufus forked/adapted the Sisyphus agent definitions and added the 19-Python-hook quality gate chain on top.

  7. opensoft + ssenart naming collision: No relationship; two authors independently chose "oh-my-claude*" naming from different parent traditions (oh-my-opencode orchestration vs oh-my-posh terminal theming). Documented as a taxonomic namespace collision.