OrchestKit plugin
A large Claude Code and Cursor plugin: development skills, specialist agents and hooks with quality gates and git protection
- 299 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Hooks fire on session events and read prompts and files to decide
- Commands run tests and create commits
Install
- Works in
Manual install
/plugin marketplace add yonatangross/orchestkit
/plugin install orkRun /ork:setup after installing.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Hooks fire on session events and read prompts and files to decide
- Commands run tests and create commits
This is third-party code. Review the repository files before installing.
What it does
OrchestKit installs as one ork plugin with three layers. Skills describe patterns for RAG, FastAPI, React, testing, security and database design and load on demand. Agents such as backend-architect and security-auditor take tasks matching their specialty. Hooks on session events block writing secrets, editing protected files, risky git operations and oversized files. The /ork:implement, /ork:review-pr, /ork:verify and /ork:commit commands run multi-agent implementation, review and commits with checks.
Who it is for. For Claude Code developers who want a ready process with guardrails rather than individual skills.
Good fit when
- You want automatic blocks on committing to main and writing secrets
- You want PR review by several agents in parallel
- Your project uses FastAPI, React or RAG and you want ready patterns
Not a fit when
- You want a lightweight set without hooks on every session event
- You use Codex or another agent where only a small subset works
Example request
/ork:review-pr check the current PR for security issues and test coverageLimitations
Hooks fire in every project where the plugin is enabled and write events to a local file that cannot be disabled separately from the plugin. Many agents need the Context7 MCP server, which the plugin does not install; without it they silently answer from model memory. Cursor gets no hooks, and Codex gets only a few skills.
How to disable. Uninstall or disable the ork plugin via /plugin in Claude Code. Individual hooks have opt-outs such as ORK_DISABLE_DEBT_TRACKER and ORCHESTKIT_SKIP_SLOW_HOOKS.
FAQ
Does the plugin send data out?
Per the README remote sync is off and no endpoint is compiled in. Hook events and metrics go to ~/.local/state/orchestkit/events.jsonl, and prompt and file contents are not recorded.
Can I install only some skills?
Yes, with npx skills add yonatangross/orchestkit and -s flags for chosen skills, but that route has no hooks or agents.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code and Codex plugin with skills for code research, tests, refactoring and independent review of finished changes
A plugin for Codex and Claude Code that runs a task through a chain of roles from planning to an independent audit
A ready-made Claude Code setup: agents, slash commands, skills, safety hooks, rules and MCP connections in one install
A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
A modular plugin set for Claude Code: skills, agents, commands and rules for Java, TypeScript, Python, PHP and AWS
MadAppGang's Claude Code plugin marketplace: agents and commands for a React frontend and a Bun backend
README in short
The README opens with a support matrix: the full set in Claude Code, the plugin without hooks in Cursor, a subset in Codex and pi. It shows install commands, a starter skill set for npx skills and the key /ork commands. Recommended MCP servers are covered with emphasis on Context7, plus a detailed section on what the hooks observe and where data is written. MIT licensed.