Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/seanrreid/rad_framework/event-metrics-mappergit 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-mapper)<a href="https://agentmods.dev/agents/seanrreid/rad_framework/event-metrics-mapper"><img src="https://agentmods.dev/badge/agents/seanrreid/rad_framework/event-metrics-mapper.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.00065 | $0.00390 |
| Opus 5 | $0.00032 | $0.00195 |
| Sonnet 5 | $0.00013 | $0.00078 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
event-metrics-mapper 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
Context tool that maps the event-log read surface and returns bounded anchors for event-metrics-orchestrator.
Responsibilities
- Locate event types and fields carrying outcome, retry, and token-usage data in the event schema
- Identify existing read helpers in harness/events.js and flag gaps against required fields
- Anchor the writer/read seam: which functions freeze event provenance and which consume it
- Anchor where harness/spine.js records wave outcomes, retries, and token usage (record sites)
- Sample .agents/state/*/events.jsonl files for record shape only; never enumerate full logs
Scope
harness/events.js (read-side helpers and event schema), harness/spine.js (outcome/retry/token-usage record sites), harness/gates.yaml (outcome vocabulary), .agents/state/*/events.jsonl (shape samples only).
Output Format
file:line anchors + event-shape notes (event types, fields carrying outcome/retry/usage data, existing read helpers vs gaps) — never raw file contents, max 40 lines. Include a brief example with fields: anchor, note.
Rules
- Never read files outside the declared scope
- Never spawn sub-agents or call Task
- Never return raw file contents — always summarize to the output format
- Sample events.jsonl files for record shape only — never enumerate or quote full logs
- Stay within the 40-line output budget
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 · 31 lines · 65 tokens per session scan A 111cbf9b6c59
event-metrics-mapper is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 390 once invoked, about $0.0003 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.