A report that explains a Git change—such as a commit, branch, or pull request—by covering the earlier system, the idea, the extracted code, and a short quiz.

Use it to catch up on a diff, explain a change to a teammate, or prepare for code review. It can produce an interactive HTML page or a Markdown report.

It gives a developer the background needed to understand an agent-written change before reviewing it.

diff-visual — Skill for Claude Code by LeeJuOh/claude-code-zero

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add LeeJuOh/claude-code-zero

Claude Code

/plugin install vision-powers

Made for: Claude Code.

Or install vision-powers, the plugin that ships this one along with the rest of its 5 skills, 2 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/skills/leejuoh/claude-code-zero/diff-visual/github.svg)](https://agentmods.dev/skills/leejuoh/claude-code-zero/diff-visual)

Your own site

<a href="https://agentmods.dev/skills/leejuoh/claude-code-zero/diff-visual"><img src="https://agentmods.dev/badge/skills/leejuoh/claude-code-zero/diff-visual/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/skills/leejuoh/claude-code-zero/diff-visual"><img src="https://agentmods.dev/badge/skills/leejuoh/claude-code-zero/diff-visual.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan C 1 finding. 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.00093	$0.06103
Opus 5.5	$0.00037	$0.02441
Sonnet 5.5	$0.00019	$0.01221
Haiku 4.5	$0.00009	$0.00610

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

Security

Grade C, and why

diff-visual scanned grade C with 1 finding 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 9d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

allowed-tools: Read, Glob, Grep, AskUserQuestion, Artifact, Skill(artifact-design), Bash(git diff *), Bash(git log *), Bash(git show *), Bash(git rev-parse *), Bash(git branch *), Bash(wc -l *), Bash(gh pr diff *), Bash(

plugins/vision-powers/skills/diff-visual/SKILL.md · 428 lines

How it starts

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

Diff Visual

Catch a reader up on a change before they review it. Most code now arrives written by an agent, which means the reader has no system already in their head — so the report answers, in order: what was here before (Background), what the idea is (Intuition), how the code realises it (Code), and whether the reader actually got it (Quiz).

When to run

Your agent finished a task and you're about to push — read it, pass the quiz, then send.
A teammate's PR is waiting — read it before you form an opinion.

The quiz is a speed regulator, not a gate. Nothing blocks a push; "don't send it until you can pass" is a rule the reader keeps, not one the tool enforces. And nothing in the report says whether the change is good — that judgement is /code-review's and the reader's.

Voice: write like Martin Kleppmann — clear, flowing, each section handing off to the next. Follow every abstract sentence with something concrete.

Output is a self-contained interactive HTML page (default) or an inline markdown report. You write it directly — no templates, no intermediate JSON, no agent chains.

Instructions

Format Detection

Parse --format first:

Flag	Values	Default	Meaning
`--format`	`html` \| `md`	`html`	`html` → full interactive page at `${CLAUDE_PLUGIN_DATA}/reports/`. `md` → inline markdown report, delivered in the response
`--local`	switch	off	Force the local design-system file — capable HTML publishes to an Artifact by default
`--artifact`	switch	retained no-op alias	Already the default on capable HTML — kept so muscle memory / natural-language triggers don't break

Channel, flags, and config follow ${CLAUDE_PLUGIN_ROOT}/references/design-system/channel-decision.md — read it before writing. In short: capable HTML publishes to a claude.ai Artifact; --local (or "keep it local", "don't publish") forces the local page; md stays local unless this turn asks to publish it. Stored config: node ${CLAUDE_PLUGIN_ROOT}/scripts/config.js get --data-dir "${CLAUDE_PLUGIN_DATA}".

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

9d ago Changed · -116 lines · -31 tokens per session e735dd4fd8c8
23d ago Changed d10ad4a0dfd8
1mo ago Changed · +14 lines 3c259188671b
1mo ago First seen · 530 lines · 124 tokens per session scan C 1e78e31c8e61

Subscribe to this mod's changes

diff-visual is a skill published in the GitHub repository LeeJuOh/claude-code-zero (52 stars, last pushed 3d ago), licensed MIT. It adds 93 tokens to every session and 6,103 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Commits Git and workflow LLM Learning and teaching ai-agents anthropic claude developer-tools

caveman-commit

Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.

JuliusBrussee/caveman · 38 tokens

cross-repo-cache

Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…

closedloop-ai/claude-plugins · 81 tokens

git-expert

Expert-level Git version control with advanced workflows, branching strategies, and best practices for team collaboration. Use when the user mentions version control, collaboration, or workflow, or when the task involves Essential Git Commands, Advanced Git Techniques, Branching Strategies, or Conflict Resolution.

personamanagmentlayer/pcl · 57 tokens

diff-visual