E
egorpol/claude-orchestrator
Claude Code as orchestrator: skills + CLI to delegate work to Codex and Cursor agents (quota-aware,…
View on GitHub (unreachable when checked on 2026-11-12)This link returned 404 on 2026-11-12
- Star count
- 0 ★ · egorpol/claude-orchestrator · read from the GitHub search API · (checked 2026-11-06 20:00:43)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
egorpol/claude-orchestrator;first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# claude-orchestrator
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Claude Code as orchestrator, Codex CLI and Cursor's headless agent as workers. This repo holds user-level Claude Code skills, a hook and session rules. A symlink from ~/.claude/skills/ makes them available in every project on a machine.
## Why this exists
This is my own workflow, tuned to my setup. Cursor is my IDE, Claude Code runs inside it as the main agent, and Codex CLI and Cursor's agent run on their own subscriptions. Claude's quota runs out first. So Claude orchestrates: it keeps design, data checks and review, and hands mechanical work to whichever pool has quota to spare. The rest of the repo cuts what Claude's own sessions cost, mostly by keeping them short.
It is a snapshot, published in case parts of it are useful to someone else. It is not a general-purpose tool. It assumes Linux, openusage for quota data, and Codex and Cursor subscriptions, and it changes whenever my workflow does. Versions are in the CHANGELOG.
## What it achieved so far
These figures come from 67 Claude Code sessions across twelve projects, 2026-10-09 to 2026-10-30; the per-session numbers are in field results. Cost units weigh tokens by API price: input 1, cache read 0.1, cache write 2, output 5. Each session did different work, so the comparisons are per call, not controlled experiments.
Short sessions with handoffs. The baseline was one 13-hour session: 389 calls, with context growing to 779k tokens. Each call re-reads everything before it, so cost grows with the square of session length; cache re-reads were 98% of its tokens. It averaged 67.4k cost units per call. The 66 sessions since averaged 23.4k (about 65% less). Through 2026-10-20, those that did one item from a HANDOFF.md ran 16.5k–31.6k; the three above 27k each let that one item grow past 240k. The rules and the hook push for one work item per session.
Idle cache rebuilds. After an hour idle, the prompt cache expires, and the next turn rewrites the whole context at twice the input price. That happened in 18 of the 69 sessions and cost 7.4% of all logged units (10.1M of 136.9M): none among the eleven from 2026-10-20 to 10-26, three among the twenty from 10-26 to 10-30, one among the two from 10-30 to 10-31. The hook now holds the first typed prompt after an hour idle and suggests /clear; it first fired live on 2026-10-13. Slash commands and picker answers pass: three earlier rebuilds came from a /field-report typed after the break, and all four since 10-26 from a picker answered after one, which --attention now flags by marking the waiting Cursor window.
No polling. In the baseline, 40 status checks cost 15.3% of the session. A finished delegate run now puts its status, at most 20 lines, into the task notification.
Delegation.
On the baseline day, Cursor Auto used about 5× fewer tokens per run than Codex at xhigh effort, and moved its quota pool about 1 point over 9 runs.
Codex later built an 887-line module with 48 tests in 16 minutes, with no fix round.
Cursor Auto built a 15-file feature in 2 rounds with 0 review findings.
A bulk pass labelled 6,529 rows with 0 failures for about 2.7 points of the Cursor Auto pool.
Cross-vendor review. On the module run, Cursor's review and Claude's own read each found a bug the other missed. Reviews also approved a wrong brief twice, so reviewers are now asked to challenge the brief.
## Why this exists
This is my own workflow, tuned to my setup. Cursor is my IDE, Claude Code runs inside it as the main agent, and Codex CLI and Cursor's agent run on their own subscriptions. Claude's quota runs out first. So Claude orchestrates: it keeps design, data checks and review, and hands mechanical work to whichever pool has quota to spare. The rest of the repo cuts what Claude's own sessions cost, mostly by keeping them short.
It is a snapshot, published in case parts of it are useful to someone else. It is not a general-purpose tool. It assumes Linux, openusage for quota data, and Codex and Cursor subscriptions, and it changes whenever my workflow does. Versions are in the CHANGELOG.
## What it achieved so far
These figures come from 67 Claude Code sessions across twelve projects, 2026-10-09 to 2026-10-30; the per-session numbers are in field results. Cost units weigh tokens by API price: input 1, cache read 0.1, cache write 2, output 5. Each session did different work, so the comparisons are per call, not controlled experiments.
Short sessions with handoffs. The baseline was one 13-hour session: 389 calls, with context growing to 779k tokens. Each call re-reads everything before it, so cost grows with the square of session length; cache re-reads were 98% of its tokens. It averaged 67.4k cost units per call. The 66 sessions since averaged 23.4k (about 65% less). Through 2026-10-20, those that did one item from a HANDOFF.md ran 16.5k–31.6k; the three above 27k each let that one item grow past 240k. The rules and the hook push for one work item per session.
Idle cache rebuilds. After an hour idle, the prompt cache expires, and the next turn rewrites the whole context at twice the input price. That happened in 18 of the 69 sessions and cost 7.4% of all logged units (10.1M of 136.9M): none among the eleven from 2026-10-20 to 10-26, three among the twenty from 10-26 to 10-30, one among the two from 10-30 to 10-31. The hook now holds the first typed prompt after an hour idle and suggests /clear; it first fired live on 2026-10-13. Slash commands and picker answers pass: three earlier rebuilds came from a /field-report typed after the break, and all four since 10-26 from a picker answered after one, which --attention now flags by marking the waiting Cursor window.
No polling. In the baseline, 40 status checks cost 15.3% of the session. A finished delegate run now puts its status, at most 20 lines, into the task notification.
Delegation.
On the baseline day, Cursor Auto used about 5× fewer tokens per run than Codex at xhigh effort, and moved its quota pool about 1 point over 9 runs.
Codex later built an 887-line module with 48 tests in 16 minutes, with no fix round.
Cursor Auto built a 15-file feature in 2 rounds with 0 review findings.
A bulk pass labelled 6,529 rows with 0 failures for about 2.7 points of the Cursor Auto pool.
Cross-vendor review. On the module run, Cursor's review and Claude's own read each found a bug the other missed. Reviews also approved a wrong brief twice, so reviewers are now asked to challenge the brief.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/egorpol-claude-orchestrator/)
- Source
- github · https://github.com/egorpol/claude-orchestrator
- Browse by field
- Open source
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.