pr-lens

pr-lens is a skill for Claude Code, Codex from NousResearch/hermes-agent. It costs 15 tokens per session (2,498 once invoked), scanned A, original, MIT.

A tool that turns a description of code changes into animated SVG diagrams of diffs, architecture, or data flows. It is for explaining changes, not finding bugs or reviewing security risks.

In plain words
What is it for?
Use it to create diagrams for pull requests, explain a code change, or show relationships and data movement in a codebase.
Why use it?
It helps readers understand how a change moves through a system when a text diff is difficult to follow.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create diagrams for pull requests, explain a code change, or show relationships and data movement in a codebase.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nousresearch/hermes-agent/pr-lens
About the project

Hermes Agent is an AI assistant that learns from its use by creating and improving skills, retaining knowledge, searching past conversations, and adapting to its users. It is for people who want to run an agent through a terminal or messaging platforms while connecting it to different AI models and scheduled tasks.

NousResearch/hermes-agent · 245,160 stars · on GitHub · hermes-agent.nousresearch.com

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 NousResearch/hermes-agent --skill pr-lens
Clone the repo
git clone --depth 1 https://github.com/NousResearch/hermes-agent

Made for: Claude Code, Codex.

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 pr-lens

README.md
[![agentmods](https://agentmods.dev/badge/skills/nousresearch/hermes-agent/pr-lens/github.svg)](https://agentmods.dev/skills/nousresearch/hermes-agent/pr-lens)
Your own site
<a href="https://agentmods.dev/skills/nousresearch/hermes-agent/pr-lens"><img src="https://agentmods.dev/badge/skills/nousresearch/hermes-agent/pr-lens/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 pr-lens

Your own site · 80×15
<a href="https://agentmods.dev/skills/nousresearch/hermes-agent/pr-lens"><img src="https://agentmods.dev/badge/skills/nousresearch/hermes-agent/pr-lens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,498 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.00015 $0.02498
Opus 5 $0.00008 $0.01249
Sonnet 5 $0.00003 $0.00500
Haiku 4.5 $0.00002 $0.00250

Measured today against content hash e5fbe22d2987, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-14, from the pricing page.

Security

Grade A, and why

pr-lens 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.

optional-skills/software-development/pr-lens/SKILL.md · 146 lines

How it starts

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

PR Lens Skill

PR Lens draws code as visually rich animated diagrams: diffs, architecture, data flows. You describe the diff or codebase as one JSON document (lanes, nodes, edges, ordered flows) and the CLI renders it as animated SVGs. There is no findings lens — PR Lens is a comprehension layer, not a review bot. There is no field for a bug, risk, or security note, and a document that invents one is rejected.

When to Use

  • Asked to diagram, visualise, or explain a code change or a system.
  • A pull request should carry an architecture or data-flow diagram.
  • Keywords: PR Lens, diagram, architecture, data flow, visualise, pull request.

Prerequisites

  • Node.js with npx (the CLI runs via npx @coldtea/pr-lens-cli@latest; no install step).
  • gh (GitHub CLI) — optional, only for attaching diagrams to PRs.
  • Optional canvas publishing calls the third-party service prlens.dev (see step 4b).

How to Run

Run all commands with the terminal tool from the repository root.

  1. Read the diff. When representing a code change: git diff --find-renames <base>...<head>. The base is the merge base, not the tip of the base branch. If not expressing a diff, read the code to be visualised.

  2. Write the document to .pr-lens/graph.json, following references/graph-document.md. references/example.graph.json is a valid reference with three lanes, all four delta states, a hero edge, a seven-step flow, a nested drill-down tree and a six-step walkthrough. Read it before writing your first document — quicker than reading the reference.

  3. Validate, and fix.

    npx @coldtea/pr-lens-cli@latest validate .pr-lens/graph.json
    

    Fix every failure and run it again. Do not render an invalid document; do not "work around" a failure by deleting the element it names.

  4. Render.

    npx @coldtea/pr-lens-cli@latest render .pr-lens/graph.json --theme light
    

    Render light by default unless the user requests another theme. The SVGs, the manifest and drawn.graph.json land in .pr-lens/, which the CLI adds to the repository's .gitignore. Do not commit any of it — these files are rebuilt from the diff on demand. Each SVG is named after its view, theme and content hash; manifest.json lists them by lens and view.

Read the full file on GitHub · 146 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 First seen · 146 lines · 15 tokens per session scan A e5fbe22d2987

Subscribe to this mod's changes

pr-lens is a skill published in the GitHub repository NousResearch/hermes-agent (245,160 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 2,498 once invoked, about $0.0001 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-09-14.