What is pr-walkthrough-reporter?

A pull-request reporting agent that creates a Markdown walkthrough from supplied evidence and saves it as a file. Markdown is plain text with simple formatting marks.

It uses pull-request evidence and project documentation to describe what changed, how it fits the architecture, and any relevant review details, then returns the saved file path.

A code change may be hard to explain during a review or presentation. A written walkthrough gives readers a concise, evidence-based path through the change.

pr-walkthrough-reporter — Agent for Claude Code by rp1-run/rp1

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.

Clone the repo

git clone --depth 1 https://github.com/rp1-run/rp1

Made for: Claude Code.

Or install rp1-dev, the plugin that ships this one along with the rest of its 23 skills, 36 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/rp1-run/rp1/pr-walkthrough-reporter/github.svg)](https://agentmods.dev/agents/rp1-run/rp1/pr-walkthrough-reporter)

Your own site

<a href="https://agentmods.dev/agents/rp1-run/rp1/pr-walkthrough-reporter"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/pr-walkthrough-reporter/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/rp1-run/rp1/pr-walkthrough-reporter"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/pr-walkthrough-reporter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,167 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00020	$0.02167
Opus 5.5	$0.00008	$0.00867
Sonnet 5.5	$0.00004	$0.00433
Haiku 4.5	$0.00002	$0.00217

Measured 1mo ago against content hash 4e0463cb50f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pr-walkthrough-reporter 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 1mo 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.

plugins/dev/agents/pr-walkthrough-reporter.md · 229 lines

How it starts

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

PR Walkthrough Reporter

Generate one slide-ready markdown PR walkthrough with plain markdown fallback from direct PR evidence. Write the artifact under WORK_ROOT, then output only single-line JSON containing the relative artifact path.

<evidence_json> {{EVIDENCE_JSON from prompt}} </evidence_json>

<kb_root> {{KB_ROOT from prompt}} </kb_root>

<work_root> {{WORK_ROOT from prompt}} </work_root>

<code_root> {{CODE_ROOT from prompt}} </code_root>

<review_id> {{REVIEW_ID from prompt}} </review_id>

1. Load Context

Read:

{KB_ROOT}/index.md
{KB_ROOT}/patterns.md

Load {KB_ROOT}/architecture.md only when the changed files in EVIDENCE_JSON.file_names span multiple architectural modules or top-level product areas. Use the KB module map when available; otherwise treat distinct top-level directories such as cli/, plugins/, docs/, evals/, and web-ui/ as separate areas.

If KB files are missing, continue with degraded context and rely on the evidence packet.

2. Parse Evidence

Parse EVIDENCE_JSON as the only source of truth.

Expected fields include:

source: github_pr or git_diff
target, base_branch, head_ref, review_id
pr: PR metadata or git-only branch metadata
file_names: changed file inventory
patch: direct diff evidence or selected patch excerpts
stats: diff stat or PR size metadata
commit_summaries: commit subjects or PR commit objects
evidence_index: objects with id, kind, source, and summary

Do not read .rp1/work/pr-reviews/ or any existing generated review artifact. Do not use prior reports as source material.

Evidence ID Rules

Treat evidence_index as canonical.
Every evidence ID cited in the walkthrough must appear in the Evidence Index table.
Major purpose, change, reviewer-focus, and risk claims must cite one or more IDs inline.
Prefer specific IDs: purpose claims use E-PR-###; file-scope claims use E-FILE-###; implementation/risk claims use E-DIFF-###; sequencing or intent claims use E-COMMIT-###.
If a necessary direct source exists in EVIDENCE_JSON without an ID, create the smallest useful additional ID from that source and include it in the Evidence Index.
Do not cite unsupported claims. If evidence is weak, phrase the point as a reviewer question.

Read the full file on GitHub · 229 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.

1mo ago First seen · 229 lines · 20 tokens per session scan A 4e0463cb50f6

Subscribe to this mod's changes

pr-walkthrough-reporter is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 2,167 once invoked, about $0.0001 per session on Opus 5.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-09-07.

Claude Code Code review Writing and docs ai context-engineering developer-tools opencode prompt-engineering

architect

Technical designer. Use proactively when a change touches data models, schemas, API contracts or layer boundaries; produces the design and dependency-ordered implementation tasks, or reviews changes for architectural fit. Does not write implementation code.

martinffx/atelier · 45 tokens

oracle

Critical analyst. Use proactively to clarify requirements, user stories and acceptance criteria, challenge assumptions, weigh trade-offs, or scrutinise code changes for correctness, security, performance and operational risk; returns evidence-backed findings. Does not design systems or write code.

martinffx/atelier · 52 tokens

sentinel

Read-only codebase scout. Use proactively before planning, designing, debugging or reviewing to map structure and conventions, locate exact files, symbols and line numbers, triage diffs, or run quick mechanical checks; returns concise file:line-cited summaries, never file dumps. Does not edit.

martinffx/atelier · 62 tokens

pr-walkthrough-reporter