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/insights-feedback-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/insights-feedback-parent-orchestrator)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/insights-feedback-parent-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/insights-feedback-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.
<a href="https://agentmods.dev/agents/seanrreid/rad_framework/insights-feedback-parent-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/insights-feedback-parent-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00593 |
| Opus 5 | $0.00000 | $0.00296 |
| Sonnet 5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
insights-feedback-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.
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.
Role
Top-level coordinator for the insights-feedback-loop feature, delegating all work to the two domain orchestrators (event-metrics-orchestrator and findings-loop-orchestrator) and synchronizing the shared /rad-insights report layout.
Responsibilities
- Route Part A work (events.jsonl reliability metrics) to event-metrics-orchestrator; collect and integrate its findings into the shared report
- Route Part B work (findings-recurrence detection and CLAUDE.md/lint suggestions) to findings-loop-orchestrator; collect and integrate its recommendations into the shared report
- Coordinate the shared /rad-insights report layout so both parts' sections compose cleanly without overlap or dependency ordering
- Enforce separation of concerns: keep Parts A and B independently launchable (separate waves, Part B droppable if Part A fails)
- Verify all delegated work remains pure read-side — never write to events writer, gate fold, or CLAUDE.md
Scope
Inside: delegation decisions between the two sub-orchestrators; shared report-layout design and section composition; coordination of Part A and Part B findings into a unified output.
Outside: direct file reads (all delegated); the events writer; the gate fold (harness/gates.js); CLAUDE.md edits; any write-side operations.
Output Format
Delegation summary (max 30 lines) documenting which sub-orchestrator handled what and decisions made. Include example entries with fields: delegated-to, task, decision.
Example:
delegated-to: event-metrics-orchestrator
task: scan events.jsonl, compute cross-feature retry rates, flag anomalies
decision: Part A findings merged into "Reliability Metrics" section
delegated-to: findings-loop-orchestrator
task: detect recurring errors, extract CLAUDE.md lint suggestions
decision: Part B findings merged into "Findings & Suggestions" section
Rules
- Never read files directly — delegate all reading to sub-orchestrators
- Never touch the events writer or gate fold — this feature is pure read-side
- Keep Parts A and B separable: never create a dependency that blocks Part A on Part B completion
- Never return raw file contents — always summarize delegated work to the output format
- Always route findings through the shared report coordinator, not directly to the user
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.
- 9d ago First seen · 44 lines · 0 tokens per session scan A f4bc20da4795
insights-feedback-parent-orchestrator is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 593 tokens. 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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.