render-review

render-review is a skill for Claude Code from ApurvBazari/claude-plugins. It costs 78 tokens per session (1,120 once invoked), scanned A, original, MIT.

A renderer that turns already-computed code-review findings into a self-contained interactive HTML report.

In plain words
What is it for?
Use it to render findings, optionally reconcile them with an earlier review, and include context from a Git diff or project plan.
Why use it?
It separates displaying review results from finding or recalculating issues, helping preserve a fixed review result.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the lens plugin — 4 skills, 6 agents shipped together

Good fit Use it to render findings, optionally reconcile them with an earlier review, and include context from a Git diff or project plan.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/apurvbazari/claude-plugins/render-review
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.

Any agent
npx skills add ApurvBazari/claude-plugins --skill render-review
Clone the repo
git clone --depth 1 https://github.com/ApurvBazari/claude-plugins

Made for: Claude Code.

Or install lens, the plugin that ships this one along with the rest of its 4 skills, 6 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.

agentmods badge for render-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/apurvbazari/claude-plugins/render-review/github.svg)](https://agentmods.dev/skills/apurvbazari/claude-plugins/render-review)
Your own site
<a href="https://agentmods.dev/skills/apurvbazari/claude-plugins/render-review"><img src="https://agentmods.dev/badge/skills/apurvbazari/claude-plugins/render-review/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.

agentmods 80×15 button for render-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/apurvbazari/claude-plugins/render-review"><img src="https://agentmods.dev/badge/skills/apurvbazari/claude-plugins/render-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,120 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00078 $0.01120
Opus 5.5 $0.00031 $0.00448
Sonnet 5.5 $0.00016 $0.00224
Haiku 4.5 $0.00008 $0.00112

Measured today against content hash 9c31205a8bd6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

render-review 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 today.

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.

lens/skills/render-review/SKILL.md · 69 lines

How it starts

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

Render Review — Pure HTML Render of a review-findings Object

You are invoked by an orchestrator (not a human). You take a review-findings object that has ALREADY been computed (by lens:engine), render it to a self-contained interactive HTML review document, and return the written path. You are stateless and write-once: the only file you create is the caller's outputPath. You never write review-state.json, never create a task list, and never re-run finders.

Your inputs (supplied in context by the caller)

  • findings — the current review-findings object (required).
  • priorFindings — a prior-run review-findings object (optional; enables reconcile).
  • diffRef — a git ref/range to read for annotated diff hunks (optional).
  • spec / plan / adherence — intent for the adherence matrix (optional).
  • outputPath — the absolute path to write the HTML (required; create the dir if absent).
  • findings.emptyScope — the discriminator for nothing to review (true means the caller's scope was empty; false/absent means an ordinary review). Full contract: ../engine/references/engine-api.md.

Step 1: Reconcile (compute-only, in memory)

If findings.emptyScope is true, return noop: nothing to review and write NO artifact.

If priorFindings is supplied, reconcile findings against it per ../review/references/reconcile.md § Orchestrator mode — fingerprint by dimension + normalized claim + stable context, label each finding fixed | still-open | new | possibly-resolved, and compute delta {fixed,new,stillOpen} + severityTrend. Write NOTHING. If priorFindings is absent, skip — this is a clean first pass (no iteration labels, no trend).

Step 2: Assemble the review-model

Build the review-model per ../review/references/review-model-assembly.md: narrative spine + adherence (from the adherence block / requirements-dimension findings) + findings[] (each with iteration, status, location, claim, detail, suggestedFix) + files[].risk + diffHunks[] (read diffRef if supplied; omit the panel if unavailable) + derived verdict (from recommendedEscalation). Apply omit-empty; never stub.

Read the full file on GitHub · 69 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. today Changed · -7 tokens per session 9c31205a8bd6
  2. 1mo ago First seen · 69 lines · 85 tokens per session scan A 8cddd7d4ec75

Subscribe to this mod's changes

render-review is a skill published in the GitHub repository ApurvBazari/claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 1,120 once invoked, about $0.0003 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-08-31.