105 skills · 36 agents · 218 hooks

Explore the Docs → · OrchestKit Community →
_{Skill browser, demo gallery, setup wizard}

• Quick Start
• Why OrchestKit?
• What You Get
• Key Commands
• Configuration
• What OrchestKit observes
• Install
• FAQ
• Development
• What's New
• Community

/plugin marketplace add yonatangross/orchestkit
/plugin install ork

Then start your personalized onboarding:

/ork:setup

The setup wizard scans your codebase, detects your tech stack, recommends skills for your needs, configures MCP servers, and creates a readiness score — all in one command.

Every Claude Code session starts from zero. You explain your stack, patterns, preferences—again and again.

OrchestKit gives Claude persistent knowledge of production patterns that work automatically:

One unified plugin, everything included.

All available in a single /plugin install ork. Skills load on-demand. Hooks work automatically.

Browse everything in the Docs →

/ork:auto         # Front door: describe a goal, it routes to the right skill
/ork:setup        # Personalized onboarding wizard
/ork:implement    # Full-stack implementation with parallel agents
/ork:expect       # Diff-aware AI browser testing
/ork:review-pr    # PR review with parallel agents
/ork:verify       # Multi-agent validation
/ork:commit       # Conventional commit with pre-checks
/ork:explore      # Analyze unfamiliar codebase
/ork:remember     # Save to persistent memory
/ork:doctor       # Health check

/ork:setup detects your stack, recommends MCP servers, and writes the configuration for you.

Set "alwaysLoad": true on the first three in your .mcp.json. It skips the per-skill tool probe and shaves ~150ms off cold starts.

Skills install as files on your disk, but don't hand-edit the installed copy — it gets overwritten on update and silently diverges from the canonical playbook. The supported ways to extend (user-level skills, project skills, upstream PRs, or disabling a bundled skill) are in docs/extending-skills.md.

OrchestKit is a quality-gate plugin, so its hooks are the product rather than an add-on. This section states plainly what they see, where it goes, and how to turn each piece off.

Scope: broad and intentional. OrchestKit registers 218 hooks across 29 lifecycle events, including SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, and Stop. They are not gated to a particular framework or project type, because the gates they enforce (secret-write blocking, protected-file guards, git safety, file-size limits, agent status protocol) apply to any codebase. If you only want gates on some projects, enable the plugin per-project rather than globally.

Where data goes: a local file on your own disk.

There is deliberately no global kill switch for the local write, because the gates depend on that state (the git-safety and chain-staleness hooks read their own prior events). To stop it entirely, disable the plugin. Individual noisy hooks have their own opt-outs: ORK_DISABLE_DEBT_TRACKER, ORK_DISABLE_WORKTREE_VERIFIER, ORK_DISABLE_COORDINATION_METRICS, ORK_NO_NOTIFY, ORK_NO_STALE_SWEEP, and ORCHESTKIT_SKIP_SLOW_HOOKS among others.

Network access is opt-in and unset by default. There is no hardcoded remote host anywhere in the shipped hook bundles (grep -o 'https\?://' plugins/ork/hooks/dist/*.mjs returns nothing). An outbound call happens only if you configure a destination yourself, via one of:

• ORCHESTKIT_HOOK_URL + ORCHESTKIT_HOOK_TOKEN, which enable the manual hooks/bin/telemetry-sync.mjs CLI. It POSTs your local JSONL to your own endpoint. No hook ever invokes it; you run it by hand.
• ORK_HQ_TELEMETRY_URL, which points the telemetry HTTP sink at your own collector.
• ORK_HQ_TELEMETRY_USE_HQ_API=1 together with HQ_API_URL, the same sink aimed at a self-hosted HQ API.

The sink returns early when the URL or the token is missing, and telemetry-sync.mjs prints No ORCHESTKIT_HOOK_URL or TOKEN configured. Nothing to sync. then exits 0. There is no analytics ping, no crash reporter, and no feature-flag fetch.

What OrchestKit never reads. No OS keychain lookups, no ~/.aws/credentials, no SSH private keys, no browser cookie or login stores, no clipboard. The one place secret-shaped paths appear in the source is plugins/ork/hooks/dist/pretool.mjs, where id_rsa, .pem, .env, and credentials.json form a blocklist that stops Claude writing to them. That code denies access; it does not read those files.

Third-party MCP servers are recommendations, not bundled dependencies. The plugin ships no .mcp.json and declares no mcpServers. The table under Configuration is advisory, and /ork:setup asks before writing anything.

/plugin install ork

No tiering. No version confusion. Just one powerful plugin.

Not on Claude Code? Pull the skills into any agent (Cursor, Codex, OpenCode, …) via skills.sh:

npx skills add yonatangross/orchestkit

Codex uses its own plugin format, skill picker, and standalone role configuration. Add OrchestKit's Codex marketplace, then install the small portable workflow pack:

codex plugin marketplace add yonatangross/orchestkit --ref main --sparse .agents/plugins --sparse plugins/ork-codex
codex plugin add ork-codex@orchestkit-codex

Restart Codex after installation. Invoke a workflow explicitly with $ork-brainstorm, $ork-explore, $ork-assess, $ork-verify, or $ork-review-pr; their narrow descriptions also let Codex select the relevant workflow automatically.

The plugin intentionally ships roles as templates because Codex loads custom roles from ~/.codex/agents/, not from a plugin manifest. From an OrchestKit checkout, run this one-time, non-overwriting install:

plugins/ork-codex/scripts/install-codex-roles.sh ~/.codex/agents

It installs ork_explorer, ork_implementer, ork_reviewer, and ork_verifier; restart Codex before spawning them.

/plugin list
/plugin uninstall ork && /plugin install ork

npm run build      # Build plugins from src/
npm test           # Run all tests

Edit src/ and manifests/, never plugins/ (generated).

See CONTRIBUTING.md for details.

v9.7.0 · 2026-08-05

• visualize-plan: make DASHBOARD a first-class archetype (#3275)
• hooks: validate agent spawn targets against the real registry (#3280)
• security: audit every tracked lockfile, not four of six (#3274)
• worktree: fix a silent no-op and remove the dead worktree CLI (#3282)
• worktree: share one node_modules across worktrees (#3281)

v9.6.1 · 2026-08-04

• deps: clear the npm-audit wave via in-range transitive updates (#3272)

v9.6.0 · 2026-08-03

• codex: add native OrchestKit adapter (#3265)

v9.5.4 · 2026-08-03

• ci: run the demos' 284 tests, stop chmod churn on .mjs (#3262)
• deps-dev: bump jsdom from 29.1.1 to 30.0.1 in /orchestkit-demos (#3259)
• deps-dev: bump the npm-minor-patch group across 1 directory with 3 updates (#3258)
• deps-dev: bump the npm-minor-patch group in /src/hooks with 2 updates (#3254)
• deps: bump the npm-minor-patch group in /src/mcp-server with 2 updates (#3255)
• …and 2 more (see CHANGELOG.md)

v9.5.3 · 2026-08-03

• deps-dev: bump @types/node in the npm-minor-patch group (#3253)
• contributing: add entry-point section and fork-CI expectation note (#3250)
• fix nonexistent scripts/hooks path in SECURITY.md (#3248)

v9.5.2 · 2026-08-02

• hooks: branch-switch awareness in git-validator protection (#3246)
• glob the five orphan test dirs into blocking coverage (#3245)

v9.5.1 · 2026-08-02

• skills: never block a user-typed invocation (#3243)

v9.5.0 · 2026-08-01

• hooks: nudge TaskCreate on 3+ step work and measure compliance (#3232)
• docs-site: fix count and command drift at source, add a drift gate (#3231)
• skills: keep user-typed fork skills interactive on CC 2.1.218+ (#3239)
• tests: dead E2E wiring, gitignore-aware gates, warn ratchet (#3236)
• evals: retire the prose-grading eval, wire the nudge reader (#3237)
• …and 3 more (see CHANGELOG.md)

See CHANGELOG.md for the full release history.

Join the Building with AI community for AI dev tips, OrchestKit support, and connecting with other builders:

Names and audiences match what yonyon.ai renders, so the two surfaces cannot drift. Every link resolves through yonyon.ai/go/*, so a rotated invite never needs a README change and no raw invite is published here.

OrchestKit is built and maintained by Yonatan Gross — Yonyon AI, an AI consulting practice. It is the toolkit extracted from real client work, not a side project: the patterns here are the ones that survived shipping.

It stays MIT and free. Nothing is gated, and none of the below changes that.

Working out where AI actually fits in your business? The AI readiness audit is a free assessment that maps your workflows and returns a prioritized report — the same diagnostic that opens a consulting engagement.

Want the toolkit running properly in your team? Setup, configuration, and a working agent loop tailored to your stack is something I do as a fixed-scope engagement. Start a discussion or reach out through the community.

Security policy and reporting: SECURITY.md.