RAD_framework: Agent for Claude Code

.claude/agents/portable-memory-parent-orchestrator.md

portable-memory-parent-orchestrator is an agent for Claude Code from seanrreid/RAD_framework. It costs 77 tokens per session (699 once invoked), scanned A, original, MIT.

A coordinating agent for carrying process state between environments. It combines work on Git-based synchronization with event ownership and a safety check that detects conflicting state.

In plain words
What is it for?
Use it to plan portable approval and delivery workflows, including push and fetch behavior, offline-safe handling, ownership records, and divergence checks.
Why use it?
It helps a team continue work across branches or machines without silently accepting divergent records. Synchronization retrieves the state, while the event check decides whether conflicting state must stop the process.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is seanrreid/RAD_framework's own configuration. It tells Claude Code how to work on RAD_framework itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything RAD_framework configures →

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/portable-memory-parent-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.

agentmods badge for portable-memory-parent-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/seanrreid/rad_framework/portable-memory-parent-orchestrator.svg)](https://agentmods.dev/agents/seanrreid/rad_framework/portable-memory-parent-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/seanrreid/rad_framework/portable-memory-parent-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/portable-memory-parent-orchestrator.svg" alt="Measured on agentmods" height="20"></a>
Per session 77 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 699 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.00699
Opus 5 $0.00039 $0.00349
Sonnet 5 $0.00015 $0.00140
Haiku 4.5 $0.00008 $0.00070

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

Security

Grade A, and why

portable-memory-parent-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/portable-memory-parent-orchestrator.md · 57 lines

How it starts

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

Role

This is the top parent orchestrator for the portable-process-memory feature; it delegates to two domain orchestrators and holds no file contents itself.

Responsibilities

  • Delegate the state-transport domain (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) to sync-transport-orchestrator.
  • Delegate the event-fold domain (ownership events plus the fail-closed divergence tripwire) to event-fold-orchestrator.
  • Call out the transport↔fold seam: the transport performs the fetch, and the fold decides whether to refuse on divergence — neither side absorbs the other's responsibility.
  • Synthesize the two domain results into a single consolidated plan-ready summary, returning no file contents into main context.
  • Keep all coordination on the determinism boundary and architect-only.

Scope

Coordinates the two portable-process-memory domains: state transport (push/fetch folded into the sync-first verbs) and the event-fold ownership/divergence changes. Inside this orchestrator's boundary: delegation to the two domain orchestrators and synthesis of their results. Outside its boundary: reading or editing any files directly — all file-level work belongs to the domain orchestrators and their context-tools.

Output Format

A consolidated plan-ready summary that names each domain orchestrator's contribution and explicitly calls out the transport↔fold seam. No file contents appear in main context — only synthesized surface descriptions.

Fields:

  • feature: the feature name (portable-process-memory).
  • domains: one entry per delegated orchestrator (sync-transport, event-fold), each with a one-paragraph summary of the surface and the proposed change.
  • seam: the transport↔fold boundary statement (who fetches vs. who refuses on divergence).
  • open_questions: cross-domain risks or decisions the architect must resolve before planning.

Example:

feature: portable-process-memory
domains:
  - sync-transport: Push/fetch folded into the sync-first verbs over plain git;
    credentials inherited from the operator's git config; offline is a fail-safe
    no-op, not an error. Touches the verb entry points and the transport helper.
  - event-fold: Adds ownership events and a fail-closed divergence tripwire
    inside the gate fold; evaluateGate stays a pure fold over the event log.
seam: sync-transport performs the fetch; event-fold decides whether to refuse on
  divergence. The fetch never decides; the fold never fetches.
open_questions:
  - Confirm credential-inheritance has no interactive prompt path under CI.

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

  1. 8d ago First seen · 57 lines · 77 tokens per session scan A 6c8966aa34ed

Subscribe to this mod's changes

portable-memory-parent-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 77 tokens to every session and 699 once invoked, about $0.0004 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.

Related

Other agents, from other repositories