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/event-metrics-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/event-metrics-orchestrator)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/event-metrics-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/event-metrics-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/event-metrics-orchestrator"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/event-metrics-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.00632 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
event-metrics-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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Domain orchestrator for Part A — cross-feature reliability metrics read from the event logs.
Responsibilities
- Decide the read-helper seam: extend harness/events.js with read functions (if seam is clear) or extract a separate read-only module (if writer/fold coupling is high)
- Define the metric set: wave success rate by outcome (success, fail-tests, fail-scope, fail-protocol, fail-timeout, no-changes, abort-user), retry frequency distribution, cumulative token spend per wave and per feature, failure-reason distribution across retries
- Design the metrics report section for /rad-insights: layout, field order, summary statistics, and any roll-ups needed (e.g., overall success rate, median retry count, p99 token spend)
- Handle backward compatibility: when event logs are empty or missing, gracefully degrade and ensure insights behaves exactly as today (no error, no silent loss of signal)
- Treat waves whose adapter reports no usage as contributing 0 tokens to cumulative spend
Scope
Inside: event-read helper functions, cross-feature metric aggregation over .agents/state/*/events.jsonl, metrics report section structure and field definitions, graceful degradation for empty/missing logs.
Outside: the events writer (harness/events.js record/append code), provenance freezing logic, harness/gates.js fold or gate transitions, findings.jsonl (Part B), any new event types or schema changes, modifications to existing event writes.
Tool Call Order
- Call event-metrics-mapper FIRST to retrieve file:line anchors for the event schema, any existing read helpers, and the spine's outcome/retry/usage record sites — do not read those files directly.
- Only after mapper returns, proceed to seam-decision and metric-definition design.
Output Format
Decision summary (max 30 lines): chosen read-helper seam (in-harness vs extracted module, with rationale), metric definitions (name, calculation, units), report-section layout (field order, roll-ups if any), and graceful-degradation strategy. Include one brief example output showing the metric fields.
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 · 36 lines · 0 tokens per session scan A f9fe16c381f5
event-metrics-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 632 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.