What is stateful-relay-orchestrator?

A coordination guide for dividing bounded work between GPT and Native Codex through a durable mailbox called Stateful Relay. GPT plans and reviews, Native Codex executes, and Relay stores task status and results.

Use it to dispatch approved tasks, retrieve execution evidence, inspect progress, and resume recoverable work through the existing Relay system.

It keeps delegated work recoverable and separates planning, execution, delivery tracking, and review. This avoids treating a delivery acknowledgement as proof that the work was checked.

stateful-relay-orchestrator — Skill by yipp2025-codex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add yipp2025-codex/local-codex-bridge --skill stateful-relay-orchestrator

Clone the repo

git clone --depth 1 https://github.com/yipp2025-codex/local-codex-bridge

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yipp2025-codex/local-codex-bridge/stateful-relay-orchestrator/github.svg)](https://agentmods.dev/skills/yipp2025-codex/local-codex-bridge/stateful-relay-orchestrator)

Your own site

<a href="https://agentmods.dev/skills/yipp2025-codex/local-codex-bridge/stateful-relay-orchestrator"><img src="https://agentmods.dev/badge/skills/yipp2025-codex/local-codex-bridge/stateful-relay-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yipp2025-codex/local-codex-bridge/stateful-relay-orchestrator"><img src="https://agentmods.dev/badge/skills/yipp2025-codex/local-codex-bridge/stateful-relay-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 595 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.00595
Opus 5.5	$0.00016	$0.00238
Sonnet 5.5	$0.00008	$0.00119
Haiku 4.5	$0.00004	$0.00060

Measured 2mo ago against content hash f4dd8ed7d534, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

stateful-relay-orchestrator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skill-payload/stateful-relay-orchestrator/SKILL.md · 44 lines

How it starts

The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Stateful Relay Orchestrator

Use this skill only with the existing Stateful Relay and Operator contract.

Authority

GPT is the planning and review authority. GPT decides what should happen, dispatches through the fixed Relay surface, and independently reviews returned evidence. ACK is delivery acknowledgement, not review.
Relay is the durable state and notification authority. Relay owns task lineage, claim and result transitions, correlation, and delivery state.
Native Codex is the execution authority. A normal Native Codex session claims bounded work and reports execution and evidence through Relay.
Operator is a facade only. Operator has no execution authority.

GPT-side workflow

dispatch sends the existing fixed read-only classroom task.
dispatch_bounded_write may be used only after a separate explicit authorization and only for the fixed install_stateful_relay_orchestrator_skill_v1 operation. The caller supplies no path, target root, leaf, cwd, shell, process, command, environment, credential, or arbitrary prompt.
results reads the durable Codex result body and evidence from Relay. Do not treat a notification acknowledgement as a review.
status reads bounded Relay state without executing, acknowledging, reclaiming, or reviewing work.
resume reads recoverable Relay inbox state and does not silently retry or create a second task.

For every result, verify task identity, project identity, client request identity, request/body hashes, revision, operation, target scope, correlation, and the reported authority attribution. For bounded writes, also verify the exact payload manifest, changed paths, collision status, before/after manifests, and independent readback before review.

Native Codex-side workflow

inbox claims only the task selected by the authenticated Native Codex mailbox.
report submits the result and evidence for the current claim through Relay.

Native Codex must revalidate the fixed operation, deployment-owned target mapping, canonical physical scope, frozen payload manifest, collision state, and correlation before any authorized mutation. Any mismatch is a failed, fail-closed result. Do not use a fallback shell, subprocess, arbitrary filesystem path, or a second mutation to repair a failed result.

Read the full file on GitHub · 44 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 44 lines · 40 tokens per session scan A f4dd8ed7d534

Subscribe to this mod's changes

stateful-relay-orchestrator is a skill published in the GitHub repository yipp2025-codex/local-codex-bridge (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 595 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents

stateful-relay-orchestrator next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
stateful-relay-orchestratoryipp2025-codex/local-codex-bridge	Skill	2	2mo ago	Apache-2.0	A	40	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	100k	today	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	3d ago	MIT	A	200	Claude Code, Codex
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	315k	6d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code