codex-exec-bridge
Skill41 starsChanged 2 months agoMITView on GitHub
Use when needing codex-exec-worker 브리지 에이전트 실행 프로토콜 — CLI 호출, 상태 파일, 게이트 검증, 에러 복구, 팀 통신
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- bootstrapSkill
- create-botSkill
- create-discord-botSkill
- create-slack-botSkill
- helpSkill
- initSkill
- install-hooksSkill
- meetingsSkill
- promptSkill
- self-updateSkill
- setupSkill
- shared-memorySkill
- slack-bridgeSkill
- slack-configureSkill
- thiscode-agySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 55
Use this skill when you need to execute tasks through the Codex CLI bridge with sandboxed execution, state tracking, and dynamic gate …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Codex Exec Bridge — Execution Protocol (Entry Point)
pumasi-job-worker.js 패턴을 codex-exec-worker 에이전트에 통합. codex CLI를 샌드박스 없이 실행하고, 상태 파일로 추적하며, Dynamic Gate로 결과를 검증합니다.
서브파일 목록
| 파일 | 내용 | 섹션 |
| 01-cli-invocation.md | Codex CLI 기본 호출, reasoning effort, 플래그, 타임아웃 | §1 |
| 02-status-file.md | 상태 파일 프로토콜 (위치, atomic write, 상태 머신) | §2 |
| 03-dynamic-gate.md | Dynamic Gate 통합 (순서, 결과 형식, FAIL 흐름) | §3 |
| 04-error-recovery.md | 에러 복구 (autofix 프롬프트, 재시도 예산, 에스컬레이션) | §4 |
| 05-team-communication.md | Agent Teams 통신 (SendMessage, progress, TaskUpdate, 전체 흐름) | §5 |
전체 실행 흐름 요약
1. 태스크 수신 (SendMessage from lead)
2. progress 0% 업데이트
3. pending 상태 파일 작성 (atomic write)
4. codex exec 실행 (timeout 300s)
5. running 상태 파일 업데이트
6. progress 50% 업데이트
7. Dynamic Gate 실행 (tsc → build → test → lint)
8. PASS: report.json 작성 → SendMessage(lead, done) → TaskUpdate(completed)
9. FAIL: autofix 프롬프트 생성 → codex exec 재실행 (최대 2회)
10. 모든 재시도 실패: SendMessage(lead, escalation) → progress 100%참조 파일
| 파일 | 역할 |
.claude/skills/dynamic-gate-verification.md | 게이트 파이프라인 상세 명세 |
pumasi-job-worker.js lines 67-71 | atomicWriteJson 구현 |
pumasi-job-worker.js lines 273-314 | 타임아웃/종료 처리 |
pumasi-job.js lines 723-762 | 게이트 실행 루프 |
pumasi-job.js lines 946-1007 | 재위임 컨텍스트 빌더 |
How to Use This Skill
Use this skill when you need to execute tasks through the Codex CLI bridge with sandboxed execution, state tracking, and dynamic gate verification. It handles multi-model execution (reasoning effort), error recovery with autofix, and team communication via Agent Teams.
Does 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.