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.
npx agentmods add skills/lttr/claude-marketplace/code-review-diffnpx skills add lttr/claude-marketplace --skill code-review-diffgit clone --depth 1 https://github.com/lttr/claude-marketplaceWrote 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.
[](https://agentmods.dev/skills/lttr/claude-marketplace/code-review-diff)<a href="https://agentmods.dev/skills/lttr/claude-marketplace/code-review-diff"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/code-review-diff.svg" alt="Measured on agentmods" height="20"></a>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.00074 | $0.01507 |
| Opus 5 | $0.00037 | $0.00754 |
| Sonnet 5 | $0.00015 | $0.00301 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade A, and why
code-review-diff 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Pure git-native review pipeline. Resolves a diff from git-native inputs, runs the review pipeline, and produces a markdown report.
Does NOT check out branches, talk to Azure DevOps / GitHub, or post comments. PR resolution is the caller's job (see Usage).
Arguments
$ARGUMENTS is a space-separated string. Parse out optional flags first, then treat the remainder as the diff source.
| Flag | Meaning |
|---|---|
--rules <path> |
Project rules markdown file. |
--pr <number> |
PR / MR id (label only — no platform fetch). |
--ticket <id> |
Ticket / work-item id (label only). |
--name <title> |
Override inferred report title. |
--print |
Print review to stdout; skip save prompt. |
Wrappers may pre-pin any of rules_file, pr, ticket, name — user-passed flags WIN.
Input Detection
After flags are stripped, the remainder selects the diff source:
| Form | Source |
|---|---|
| empty | current branch vs base (master/main) |
staged |
git diff --staged |
path ending .diff or .patch |
local diff file |
| anything else | treat as git ref (branch / sha / tag) |
Ambiguous → ask user. Do NOT guess. Never treat a bare numeric as a PR id — PR identity is set only via --pr.
Workflow
1. Resolve input → diff file path + metadata
empty
base=$(git rev-parse --verify master 2>/dev/null && echo master || echo main)
cur=$(git branch --show-current)
[ "$cur" = "$base" ] && abort "On base branch ($base). Switch to a feature branch."
git diff "$base"...HEAD > "/tmp/code-review-diff-$(date +%s).diff"
files=$(git diff --name-only "$base"...HEAD)
title="$cur"
slug="$cur"
What ships with it
1 file 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.
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.
- yesterday Changed · +1 lines 9077639bacdb
- 6d ago First seen · 142 lines · 74 tokens per session scan A 85655f2e3822
code-review-diff is a skill published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 1,507 once invoked, about $0.0004 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.
Other skills, from other repositories
verify-change
变更校验关卡。分析代码变更，检测文档同步状态，评估变更影响范围。当用户提到变更检查、文档同步、代码审查、提交前检查、diff分析时使用。在设计级变更、重构完成时自动触发。.
verify-module
模块完整性校验关卡。扫描目录结构、检测缺失文档、验证代码与文档同步。当用户提到模块校验、文档检查、结构完整性、README检查、DESIGN检查时使用。在新建模块完成时自动触发。.
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-worktree-kit
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.