ork-codex
v9.5.4Portable OrchestKit workflows for Codex: brainstorm, explore, implement, assess, verify, and review pull requests.
By Yonatan GrossLicense: MIT224 GitHub starsUpdated 9 hours ago
Directory evidence
- Runtimes
- Codex
- Parsed components
- 7 skill or MCP entries
- Source updated
- Aug 31, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Get the plugin
git clone https://github.com/yonatangross/orchestkitClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is src/codex/ork-codex/.
Compatibility: the page URL and API slug “ork-codex-2” remain stable.
- Codex: Legacy selector
ork-codex-2@agent-plugin-marketplaceremains documented for migration; install from source for this runtime.
This plugin's manifest name conflicts with another source for the same runtime. The source remains indexed, but this directory does not generate mismatched -2/-3 install commands.
Plugin files
├── .codex-plugin/plugin.json├── skills/ork-assess/SKILL.md├── skills/ork-brainstorm/SKILL.md├── skills/ork-explore/SKILL.md├── skills/ork-implement/SKILL.md├── skills/ork-review-pr/SKILL.md├── skills/ork-verify/SKILL.md└── .mcp.json
Included Skills6
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate, compare, identify trade-offs, evaluate readiness, or decide whether an approach is good enough. Do not use for a full pull-request review or to implement a chosen solution.
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request asks to brainstorm, think through options, choose an approach, evaluate trade-offs, or resolve significant uncertainty before implementation. Do not use for an already specified mechanical change.
Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request asks how a system works, where behavior lives, what changed, which dependencies matter, or for onboarding before a change. Do not use to implement or fix the code.
Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a feature that already has an agreed approach. Do not use to explore, review, or verify existing work, or to choose between approaches.
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a request asks to review a PR, review a diff, find real bugs, assess merge risk, or provide evidence-backed review findings. Do not use for implementation or style-only cleanup.
Verify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to verify, validate, prove, check readiness, run the relevant tests, or distinguish a claimed result from an observed one. Do not use to write missing tests or fix failures.
MCP servers1
- url
- https://mcp.context7.com/mcp
Plugin manifests1
{
"name": "ork-codex",
"version": "9.5.4",
"description": "Portable OrchestKit workflows for Codex: brainstorm, explore, implement, assess, verify, and review pull requests.",
"author": {
"name": "Yonatan Gross",
"url": "https://github.com/yonatangross"
},
"homepage": "https://github.com/yonatangross/orchestkit",
"repository": "https://github.com/yonatangross/orchestkit",
"license": "MIT",
"keywords": [
"orchestration",
"code-review",
"verification",
"planning"
],
"skills": "./skills/",
"mcpServers": "./mcp.json",
"interface": {
"displayName": "OrchestKit for Codex",
"shortDescription": "Evidence-first orchestration workflows for Codex.",
"longDescription": "A small, Codex-native OrchestKit pack for deliberate planning, codebase exploration, scoped implementation, assessment, verification, and pull-request review. It uses Codex skills and subagents without Claude-only commands or hooks.",
"developerName": "Yonatan Gross",
"category": "Productivity",
"capabilities": [
"Read",
"Write"
],
"defaultPrompt": "Use $ork-brainstorm to compare approaches before I implement a change."
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[ork-codex on Agent Plugins Marketplace](https://pluginsmp.com/plugins/ork-codex-2)