audit-surface-mapper

A read-only coding agent that locates where audit information is gathered and displayed.

In plain words
What is it for?
Finding the extension points for auto-clear trends in reports, session-start briefings, and approval-event counts.
Why use it?
It helps add audit summaries without changing approval records or other workflow state.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/seanrreid/rad_framework/audit-surface-mapper
Clone the repo
git clone --depth 1 https://github.com/seanrreid/RAD_framework

Made for: Claude Code.

Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 703 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00050 $0.00703
Opus 5 $0.00025 $0.00351
Sonnet 5 $0.00010 $0.00141
Haiku 4.5 $0.00005 $0.00070

Measured 3d ago against content hash d73dc6dba131, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

audit-surface-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 3d 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/audit-surface-mapper.md · 46 lines

How it starts

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

Role

Read-only context tool that maps the rad-insights aggregation, the kickoff session-start report, and the event-log read helpers for the audit-surface-orchestrator.

Responsibilities

  • Locate where /rad-insights synthesizes and outputs the report (section pattern to extend with auto-clear counts/trends); file:line anchor
  • Locate where kickoff reports active plan status at session start (the briefing section where auto-clear summary line attaches); file:line anchor
  • Identify the event-log read helper in harness/events.js that counts approved events and can be extended for policy provenance; function name + signature

Scope

Read scope: the rad-insights skill (.agents/findings.jsonl reader + report synthesis), the kickoff skill (session briefing), and the event-log read helpers in harness/events.js (the fold/read side only). Nothing outside this scope — read side only, never the event writer (recordApproval).

Output Format

Report in ≤35 lines, no raw file dumps. Structure:

  • rad-insights extension point: .claude/commands/shared/rad-insights.md line (e.g., "Step 5, after the ### Recommended Focus Areas block")
  • kickoff briefing anchor: .claude/skills/kickoff/SKILL.md line (e.g., "Step 3, after the plan status grouping")
  • event-log read helper: function name + signature from harness/events.js (e.g., reduce(history) returns { approvals } array where each carries role + recordedBy provenance)

Example output:

rad-insights: .claude/commands/shared/rad-insights.md line 165
  Pattern: Insert "### Auto-Cleared Changes" section after "### Recommended Focus Areas"
  Source: Extend the %cycle aggregation to count approved events where data.role === "policy"

kickoff: .claude/skills/kickoff/SKILL.md line 57
  Pattern: After plan status groups, add "Auto-cleared: N changes since {date}"
  Source: Call read helper to count approved events with policy provenance this session

event-read helper: harness/events.js line 129 function reduce(history)
  Returns: { approvals: [{actor, ts, role?, recordedBy?}] } — iterate to count role='policy'

Read the full file on GitHub · 46 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. 3d ago First seen · 46 lines · 50 tokens per session scan A d73dc6dba131

Subscribe to this mod's changes

audit-surface-mapper is an agent published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 7d ago), licensed MIT. It adds 50 tokens to every session and 703 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.