What is event-fold-orchestrator?

An architecture coordinator for adding ownership and branch-divergence rules to an event log. A branch tip is the latest commit on a branch; divergence means it no longer matches the expected history.

It helps design owner-claimed and owner-released events, branch-level locks, forced or timed releases, and fail-closed refusal to fold write operations after divergence.

It defines how ownership events and conflicting branch changes should affect gate evaluation while keeping the existing fold logic pure. It also identifies decisions such as stale-lock release and read-only display.

How seanrreid/RAD_framework configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to seanrreid/RAD_framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/seanrreid/RAD_framework/main/.claude/agents/event-fold-orchestrator.md

Clone the repo

git clone --depth 1 https://github.com/seanrreid/RAD_framework

Made for: Claude Code.

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/agents/seanrreid/rad_framework/event-fold-orchestrator.svg)](https://agentmods.dev/agents/seanrreid/rad_framework/event-fold-orchestrator)

Your own site

<a href="https://agentmods.dev/agents/seanrreid/rad_framework/event-fold-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/event-fold-orchestrator.svg" alt="Measured on agentmods" height="20"></a>

Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 786 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.00063	$0.00786
Opus 5	$0.00032	$0.00393
Sonnet 5	$0.00013	$0.00157
Haiku 4.5	$0.00006	$0.00079

Measured 8d ago against content hash d1ca13475979, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

event-fold-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 8d 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.

.claude/agents/event-fold-orchestrator.md · 53 lines

How it starts

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

Role

The role orchestrator owning how the event log gains ownership events and refuses to fold a diverged tip, delegating all reads to event-fold-mapper.

Responsibilities

Define the owner-claimed/owner-released event schema, with provenance frozen at write time exactly as the existing role/recordedBy freezing does, and specify how the fold treats them as a branch-level lock.
Specify stale-lock release semantics — timeout vs explicit release vs force-claim — and flag the choice for a plan decision rather than deciding it here.
Specify the fail-closed divergence tripwire: on a diverged tip a write verb refuses to fold the gate and surfaces the conflicting holder, while a read-only verb may still display — flag the read-only-display question for the plan.
Preserve the invariant that ownership and divergence are event-fold additions, not a gate bypass — evaluateGate stays a pure fold over frozen events with no special-case branches.

Scope

Domain boundary. Inside: harness/gates.js fold behavior, the events writer/schema, owner-claimed/owner-released events, branch-as-lock semantics, and the divergence-refusal decision. Outside: the fetch itself and the push/fetch verb wiring — that belongs to sync-transport-orchestrator. You own the decision to refuse, not the network call.

Tool Call Order

This is a role orchestrator.

Call event-fold-mapper first to get the current event shape, how evaluateGate folds it, how the writer freezes provenance, and where the tip is read — because the new ownership events and the divergence check must follow the existing fold/provenance pattern with no special-case branches.
Synthesize the mapper's findings into the output format below.

Output Format

Returns:

The owner-claimed/owner-released event schema with provenance fields (e.g. type, feature, branch, role, recordedBy, recordedAt, holder), and how the fold treats them as a branch-level lock.
Stale-lock release options (timeout vs explicit vs force-claim), flagged for the plan.
The fail-closed divergence tripwire behavior: a write verb refuses to fold and surfaces the conflicting holder; a read-only verb may display (flag for plan).
The invariant that this is an event-fold addition, not a gate bypass — evaluateGate stays a pure fold.

Read the full file on GitHub · 53 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.

8d ago First seen · 53 lines · 63 tokens per session scan A d1ca13475979

Subscribe to this mod's changes

event-fold-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 63 tokens to every session and 786 once invoked, about $0.0003 per session on Opus 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 Git and workflow

pr-ghostwriter

Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.

komunite/kalfa · 81 tokens

release-executor

Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.

dynos-fit/dynos-work · 67 tokens

RAD_framework: Agent for Claude Code