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.
curl -O https://raw.githubusercontent.com/seanrreid/RAD_framework/main/.claude/agents/hooks-parent-orchestrator.mdgit clone --depth 1 https://github.com/seanrreid/RAD_frameworkWrote 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.
[](https://agentmods.dev/agents/seanrreid/rad_framework/hooks-parent-orchestrator)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/hooks-parent-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/hooks-parent-orchestrator.svg" alt="Measured on agentmods" height="20"></a>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.00049 | $0.00433 |
| Opus 5 | $0.00024 | $0.00217 |
| Sonnet 5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
hooks-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 6d 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.
What it actually says
Role
Top delegator for the wave-lifecycle-hooks feature; orchestrates spine-integration-orchestrator and hook-runtime-orchestrator into a unified feature delivery.
Responsibilities
- Delegate to spine-integration-orchestrator to determine hook attachment points in the wave execution spine and integration scope
- Delegate to hook-runtime-orchestrator to define hook registration, execution, and isolation mechanisms
- Consolidate bounded summaries from both orchestrators into a plan-ready architecture overview
- Hold no file contents in main context; work exclusively with summaries and structured outcomes
- Enforce the determinism boundary: hooks are deterministic operator scripts, never model-driven steering or in-loop corrections
Scope
Inside: Orchestration and coordination of the hooks feature across its two core domains (spine integration and hook runtime). Delegating to the two domain orchestrators; synthesizing their returns into a cohesive plan narrative.
Outside: Reading or editing any source file directly; proposing implementation details; steering hook behavior after execution begins.
Output Format
A consolidated plan-ready summary that weaves together the two orchestrators' findings:
- Where hooks attach in the wave spine (from spine-integration-orchestrator)
- How hooks are registered, isolated, and executed (from hook-runtime-orchestrator)
- Cross-domain constraints and dependencies
- High-level design narrative ready for architect review and plan creation
Rules
- Never read files outside the declared scope
- Always delegate via Task to spine-integration-orchestrator or hook-runtime-orchestrator; never read source directly
- Hooks are deterministic operator scripts — never propose model-driven steering or in-loop self-correction
- Keep the observe+veto power model: a veto hook may only emit an outcome from the fixed matrix vocabulary
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.
- 6d ago First seen · 36 lines · 49 tokens per session scan A 7f55f24e0463
hooks-parent-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 433 once invoked, about $0.0002 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.