then routes your task to the right specialist. No config files. No boilerplate.
**[oh-my-claudecode](https://github.com/Yeachan-Heo/oh-my-claudecode)** (OMC) — Yeachan Heo | 19 specialist agents (architect, debugger, code reviewer, security reviewer, …) that divide work by role, plus 13 orchestration skills — autopilot, ralph, team. Magic keywords like `autopilot:` activate automatic parallel execution. | Submodule `upstream/omc`, SHA-pinned (see [Bundled Upstream Versions](#bundled-upstream-versions)); `install.sh` runs `npm i -g oh-my-claude-sisyphus@latest` and enables the `oh-my-claudecode@omc` plugin. |
| 2 | 
**[oh-my-openagent](https://github.com/code-yeongyu/oh-my-openagent)** (omo) — code-yeongyu | A multi-platform harness that routes across 8 providers (Claude, GPT, Gemini, …) by category and bridges to Claude Code via `claude-code-agent-loader` and `claude-code-plugin-loader`. Its 9 agents (Sisyphus, Atlas, Oracle, …) are adapted here as standalone `.md` files. | Not a submodule: the 9 agents live in `agents/omo/`; `install.sh` runs `npm i -g oh-my-opencode@latest` for the `omo` CLI. |
| 3 | 
**[andrej-karpathy-skills](https://github.com/forrestchang/andrej-karpathy-skills)** — forrestchang | The 4 AI-coding behavioral guidelines — Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution — always active. | `install.sh` curls `CLAUDE.md` at the pinned SHA `aa4467f`, checksum-verifies it, and appends it to `~/.claude/CLAUDE.md`. No code vendored. |
| 4 | 
**[everything-claude-code](https://github.com/affaan-m/everything-claude-code)** (ECC) — affaan-m | 278 skills + 67 agents + 94 commands + language rules upstream. my-claude installs a curated 61-skill subset (79 with the opt-in `web` lane) — stack patterns, AI/agent engineering, codebase tooling — plus 9 rule sets and slash commands like `/tdd`, `/plan`, `/code-review`, `/build-fix`. | Submodule `upstream/ecc`, SHA-pinned; `install.sh` tries `claude plugin add affaan-m/everything-claude-code` first and falls back to the submodule. |
| 5 | 
**[gstack](https://github.com/garrytan/gstack)** — garrytan | Garry Tan's sprint-process harness: 26 skills plus the `gstack` root router (27 total) — browser QA (`/qa`), scope-drift code review (`/review`), security audit (`/cso`), and the full Plan→Review→QA→Ship workflow (Boss P0 lane). Ships a compiled Playwright browser daemon for real-browser testing. | Submodule `upstream/gstack`, SHA-pinned. |
| 7 | 
**[superpowers](https://github.com/obra/superpowers)** — Jesse Vincent | Jesse Vincent's dev-process library: 14 of its 15 skills — brainstorming, systematic debugging, TDD, plan writing and execution, code-review etiquette. `dispatching-parallel-agents` is excluded because Boss and Agent Teams already own that path. | Submodule `upstream/superpowers`, SHA-pinned. |
| 8 | 
**[codeburn](https://github.com/getagentseal/codeburn)** — getagentseal | Local-first token and cost tracking over the session files Claude Code and Codex already write — no proxy, no API key, nothing leaves the machine. The usage-guard hooks install by default (`--no-codeburn-guard` opts out) with the hard cost cap disabled: it's estimated from the transcript at API list-price rates, so on a subscription plan a normal session reaches the $15 default in minutes and the guard would deny every further tool call. Edit `hardUSD` in `~/.config/codeburn/guard.json` to set a cap of your own. | `npm i -g codeburn@0.9.25`; `install.sh` also starts or reuses one shared cross-harness dashboard — see [Where to See Results](#where-to-see-results). MIT. |
| 9 | 
**[serena](https://github.com/oraios/serena)** — oraios | A language server's symbol graph over MCP: `find_symbol`, `get_symbols_overview`, `find_referencing_symbols`, `replace_symbol_body`, `insert_after_symbol` — the tokens spent scale with the symbol, not the file. | `uv tool install -p 3.13 serena-agent==1.7.0`, registered as a user-scope stdio MCP server (`serena start-mcp-server --context claude-code --project-from-cwd`). The distributed package is GPL-3.0-or-later as a whole (PyPI's MIT classifier is inaccurate); used as an external server, never vendored. |
| 10 | 
**[headroom](https://github.com/headroomlabs-ai/headroom)** — Headroom Labs | Tool-output compression: `headroom mcp serve` exposes `headroom_compress`, `headroom_retrieve`, and `headroom_stats`, so an oversized tool result never lands in the transcript whole. | `uv tool install --python 3.13 "headroom-ai[all]==0.40.0"`, registered as the `headroom` stdio MCP server; `install.sh` also starts or reuses the mutation-free persistent profile `agent-harness-shared`. Apache-2.0. |
| 11 | 
**[archify](https://github.com/tt-a1i/archify)** — tt-a1i | One agent skill that draws architecture, workflow, sequence, data-flow, and lifecycle diagrams as self-contained HTML — inline SVG, a dark/light theme toggle, a PNG/JPEG/WebP/SVG export menu, no runtime dependencies in the generated file. It also accepts pasted Mermaid as an input dialect. | Submodule `upstream/archify`, pinned at tag `v3.0.1`; `install.sh` copies the upstream `archify/` skill directory to `~/.claude/skills/archify`, so no `npx skills add` runs at install time. |
| 12 | 
**[agency-agents](https://github.com/msitarzewski/agency-agents)** — msitarzewski | 3 engineering agents with no equivalent elsewhere in the stack: AI Engineer, DevOps Automator, Multi-Agent Systems Architect. | Submodule removed 2026-07-27; the 3 agents were snapshotted into `agents/vendored/` on that date, each file carrying its upstream attribution header. MIT. |
| 13 | 
**[ast-grep](https://github.com/ast-grep/ast-grep)** — ast-grep | Structural, AST-aware code search and rewrite, so agents match code shapes instead of regex. | `npm i -g @ast-grep/cli@0.45.3`. MIT. |
| 14 | 
**[context7](https://github.com/upstash/context7)** — Upstash | Up-to-date, version-accurate library documentation, so an agent reads the real API instead of recalling one. | Hosted MCP server at `https://mcp.context7.com/mcp`, registered by `install.sh`. |
| 15 | 
**[exa](https://github.com/exa-labs/exa-mcp-server)** — Exa Labs | Neural (semantic) web search for research that keyword search misses. | Hosted MCP server at `https://mcp.exa.ai/mcp`, registered by `install.sh`. |
| 16 | 
**[grep.app](https://github.com/grep-app)** — grep.app | Code search across public GitHub repositories, for finding how a pattern is used in the wild. | Hosted MCP server at `https://mcp.grep.app`, registered by `install.sh`. |
---
## How Boss Works
Boss is the meta-orchestrator at the core of my-claude. It never writes code — it discovers, classifies, matches, delegates, and verifies.
| Phase | What Happens |
|-------|--------------|
| **0 · Discovery** | Scans agents, skills, MCP tools, and hooks at runtime into a live capability registry |
| **1 · Intent gate** | Classifies the request (trivial, build, refactor, mid-sized, architecture, research, …) and counter-proposes a skill when one fits better |
| **2 · Capability matching** | Cascades the priority chain below (P0 gstack skill → P1 exact skill → P2 specialist agent → P3 multi-agent orchestration → P4 general-purpose fallback) |
| **3 · Delegation** | Sends a 6-section structured prompt to the specialist: TASK / OUTCOME / TOOLS / DO / DON'T / CTX |
| **4 · Verification** | Reads the changed files independently, runs tests, lint, and build, cross-references the original intent, retries up to 3× on failure |
### Priority Routing
| Priority | Match Type | When | Example |
|:--------:|-----------|------|---------|
| **P0** | gstack skill | Ship / QA / deploy / security workflow | `"ship this"` → gstack `/ship` |
| **P1** | Skill match | Task maps to a self-contained skill | `"merge PDFs"` → pdf skill |
| **P2** | Specialist agent | Domain-specific agent exists | `"security audit"` → security-reviewer |
| **P3a** | Boss direct | 2-4 independent agents | `"fix 3 bugs"` → parallel spawn |
| **P3b** | Sub-orchestrator | Complex multi-step workflow | `"refactor + test"` → Sisyphus |
| **P3c** | Agent Teams | Peer-to-peer communication needed | `"implement + review"` → Review Chain |
| **P4** | Fallback | No specialist matches | `"explain this"` → general agent |
### Model Routing
| Complexity | Model | Used For |
|-----------|-------|----------|
| Top-level orchestration | `claude-opus-5-5` | Boss |
| Advisor group (read-only second opinions) | `claude-fable-5-1` | Oracle, Metis, Momus |
| Deep analysis, architecture | `claude-opus-5-5` | Sisyphus, Atlas, Hephaestus, Prometheus |
| Standard implementation | `claude-sonnet-5` | Librarian, Multimodal-Looker, OMC specialists |
| Quick lookup, exploration | `claude-haiku-4-5` | Lightweight OMC agents, simple advisory |
### Effort Tiers
Model choice sets *which* brain runs a task; the `effort:` frontmatter field sets *how hard* it thinks. Every self-owned agent declares one:
| Effort | Agents |
|--------|--------|
| `xhigh` | Boss, Oracle, Prometheus, Multi-Agent Systems Architect |
| `high` | Sisyphus, Hephaestus, Atlas, Metis, Momus |
| `medium` | Librarian, Multimodal-Looker, AI Engineer, DevOps Automator |
Skills declare effort too — `boss-briefing` runs at `medium`, `briefing-vault` at `low`. `boss-advanced` and `gstack-sprint` deliberately declare none: a skill's effort overrides the session level while it runs, which would quietly downgrade Boss mid-flow.
Precedence is `CLAUDE_CODE_EFFORT_LEVEL` (env) > frontmatter > session effort level. `xhigh` is Fable's supported ceiling; `max` is Opus-class only and silently falls back elsewhere.
### 3-Phase Sprint Workflow
For end-to-end feature implementation, Boss orchestrates a structured sprint:
| Phase | Mode | What Happens |
|-------|------|--------------|
| **1 · Design** | interactive | User decides scope · engineering review · confirm "design done" |
| **2 · Execute** | autonomous | ralph runs execution · auto code review · architect verification |
| **3 · Review** | interactive | Compare against the design doc · present comparison table · user approves or asks for improvement |
### Structured Final Report
Boss closes every working turn — one that edited files, made commits/PRs, changed configuration, or ran verification — with a structured report the reader can scan without opening a diff. Each table is emitted only when its situation actually occurred (never an empty table):
| Situation | Table | Columns |
|-----------|-------|---------|
| Files/settings changed | Changes | Target / Before / After / Rationale |
| Multiple tasks completed | Work summary | Item / Result / Evidence |
| Verification was run | Verification | Item / Expected / Actual / Verdict |
| Commits/PRs produced | Deliverables | PR / Repo / Content / Status |
| Anything unresolved | Remaining | Item / Status / Next step |
It fires only at the very end of the request — never on a turn that launches or relays background work, never as a mid-task progress update — and pure Q&A turns end normally without it. The spec lives in `boss.md § FINAL REPORT`; the `stop-final-report.js` Stop hook enforces it, judging from the harness-provided `last_assistant_message` plus the turn's origin in the transcript, blocking at most once per turn and failing open on any error.
### Named Workflows
Deterministic multi-agent workflows. `install.sh` copies them to `~/.claude/workflows/`, so they run from any project through the Workflow tool — not just from this repo.
| Workflow | What It Does | Invocation |
|----------|--------------|------------|
| **code-review-fanout** | Four dimension reviewers (correctness, security, performance, tests) fan out in parallel, then every finding is adversarially verified before it is reported | `Workflow({name: "code-review-fanout"})` — args: the review target (branch, commit range, paths). Defaults to the working-tree diff |
| **upstream-audit** | One analyst per upstream — pin delta vs origin, allowlist fit, new overlaps, security signals, health — followed by a synthesized action list | `Workflow({name: "upstream-audit"})` — for quarterly or pre-sync audits |
### How Boss discovers agents and skills
Boss does not have to remember to read anything: routing information is pushed into its context by two hooks.
| Piece | What it does |
|-------|--------------|
| **Registry v2** (`hooks/build-registry.js`) | At session start, scans every agent and skill Claude Code can load — `~/.claude/agents/**`, `~/.claude/skills/*`, the project's `.claude/agents/**` and `.claude/skills/*`, and the agents/skills of every **enabled** plugin (addressed as `
[Exa](https://exa.ai) | Free 1k req/month |
| 
Briefing Vault
Obsidian-compatible persistent memory. Every project maintains a `.briefing/` directory that auto-populates across sessions. Every path below is created and maintained by hooks:
| Path | Description |
|------|-------------|
| `INDEX.md` | Project overview with links to recent decisions and learnings. Auto-created on first session, refreshed by /boss-briefing or Stop hook fallback. |
| `state.json` | Session metadata: counters (workCounter, messageCount), lastVaultSync timestamp, sessionStartHead. Auto-managed by hooks. |
| `sessions/` | **Session summaries**, named `YYYY-MM-DD-