taskmaster
Skill520 starsChanged 9 months agoMITView on GitHub
Codex wrapper plus same-process expect PTY injector that keeps work moving until an explicit parseable done signal is emitted.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- lili-luo/aicoding-cookbooktheir own version, first seen Oct 8, 2026
- thegeekybeng/architecture-governancetheir own version, first seen Jul 21, 2026
- luluywang/claude-skillsedited, first seen Mar 23, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- luluywang/claude-skills★ 026% same
Wrote their own version · 2
- lili-luo/aicoding-cookbook★ 687same name
- thegeekybeng/architecture-governance★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Token present: no further injection.
- Distinctive: line 31
When the work is genuinely complete, the agent must include this exact line in its final response (on its own line):
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Taskmaster
Taskmaster for Codex uses session-log polling plus automatic continuation. Codex TUI does not currently expose arbitrary writable stop hooks, so this skill implements the same completion contract externally.
How It Works
- Run Codex via wrapper:
run-taskmaster-codex.shsetsCODEX_TUI_RECORD_SESSION=1and a log path. - Injector parses log events and checks completion on each
task_completeevent. - Parseable token contract:
TASKMASTER_DONE::<session_id> - Token missing:
- inject follow-up user message into the same running process via expect PTY bridge transport, using the shared compliance prompt.
- Token present: no further injection.
Parseable Done Signal
When the work is genuinely complete, the agent must include this exact line in its final response (on its own line):
TASKMASTER_DONE::<session_id>This gives external automation a deterministic completion marker to parse.
Configuration
TASKMASTER_MAX(default0): max warning count before suppression in the stop hook.0means unlimited warnings.
Fixed behavior (not configurable):
- Done token prefix:
TASKMASTER_DONE - Poll interval:
1second - Transport: expect only
- Expect payload mode and submit delay are fixed
Setup
Install and run:
bash ~/.codex/skills/taskmaster/install.sh
codex-taskmasterDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.