RAD_framework: Agent for Claude Code

.claude/agents/approval-authority-parent-orchestrator.md

approval-authority-parent-orchestrator is an agent for Claude Code from seanrreid/RAD_framework. It costs 91 tokens per session (859 once invoked), scanned A, original, MIT.

A coordinating agent for recording who approved an architecture decision and how that approval is stored. It divides the work between the approval data model and the commands that use it.

In plain words
What is it for?
Use it to plan changes involving architecture-approved events, the special architecture log, re-approval, approval fingerprints, or preserving existing data processing.
Why use it?
It keeps the approval record and the command-line behavior consistent, so each part has a clear responsibility and the approval history remains reliable.

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/approval-authority-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 approval-authority-parent-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/seanrreid/rad_framework/approval-authority-parent-orchestrator/github.svg)](https://agentmods.dev/agents/seanrreid/rad_framework/approval-authority-parent-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/seanrreid/rad_framework/approval-authority-parent-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/approval-authority-parent-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.

agentmods 80×15 button for approval-authority-parent-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/seanrreid/rad_framework/approval-authority-parent-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/approval-authority-parent-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 859 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.00091 $0.00859
Opus 5 $0.00046 $0.00430
Sonnet 5 $0.00018 $0.00172
Haiku 4.5 $0.00009 $0.00086

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

Security

Grade A, and why

approval-authority-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 9d 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/approval-authority-parent-orchestrator.md · 56 lines

How it starts

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

Role

The top parent orchestrator for the approval-authority-recording feature; it delegates to two domain orchestrators and holds no file contents itself.

Responsibilities

  • Delegate to approval-event-model-orchestrator (the architecture-approved event type, the reserved _architecture project log, the re-approval transition/fingerprint, and pure-fold preservation) and to approval-command-integration-orchestrator (the /rad-design inline-approve write site and the /rad-approve re-approval verb).
  • Hold the model↔verb seam: the event-model defines the event, writer, _architecture log, and transition; the commands call that writer and never re-implement it. Surface this seam explicitly in the synthesis.
  • Map the two sub-problems — design-audit-event (recording the architecture-approved audit event) and plan re-approval — across both orchestrators so each domain's slice of each sub-problem is visible.
  • Return a single consolidated plan-ready summary with no file contents in main context.
  • Keep all work architect-only on the approval-authority / determinism boundary.

Scope

Inside: delegation to the two domain orchestrators and synthesis of their summaries across the two sub-problems. Outside: reading or editing any files directly — all file knowledge lives in the domain orchestrators.

Output Format

A consolidated plan-ready summary delegating to the two domain orchestrators, with the model↔verb seam called out and the two sub-problems mapped across both. No file contents in main context.

Fields:

  • domains: the two orchestrators delegated to, each with its returned summary (event-model, command-integration).
  • seam: the model↔verb boundary statement (event-model defines, commands call).
  • sub_problems: each of design-audit-event and re-approval mapped to its slice in both domains.
  • invariants: cross-cutting constraints to preserve (e.g. architecture-approved is audit-only, never a fold branch).
  • plan_ready_summary: the synthesized prose for the planner.

Read the full file on GitHub · 56 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. 9d ago First seen · 56 lines · 91 tokens per session scan A c957ba57e3ea

Subscribe to this mod's changes

approval-authority-parent-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 6d ago), licensed MIT. It adds 91 tokens to every session and 859 once invoked, about $0.0005 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.