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 skills add n24q02m/claude-plugins --skill review-deltagit clone --depth 1 https://github.com/n24q02m/claude-pluginsWrote 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/n24q02m/claude-plugins/review-delta)<a href="https://agentmods.dev/skills/n24q02m/claude-plugins/review-delta"><img src="https://agentmods.dev/badge/skills/n24q02m/claude-plugins/review-delta/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.
<a href="https://agentmods.dev/skills/n24q02m/claude-plugins/review-delta"><img src="https://agentmods.dev/badge/skills/n24q02m/claude-plugins/review-delta.svg" alt="Reviewed on agentmods" width="80" 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.00022 | $0.00663 |
| Opus 5 | $0.00011 | $0.00331 |
| Sonnet 5 | $0.00004 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
review-delta 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Delta
Perform a focused, token-efficient code review of uncommitted changes and their blast radius. Use this for quick local reviews BEFORE committing. For full branch/PR reviews, use review-pr instead.
Command surface: run the local CLI through the coding harness shell. Examples
use the installed better-code-review-graph command; from a source checkout,
prefix it with uv run. No MCP mapping is required. Use
better-code-review-graph review --help for the command reference.
Steps
-
Ensure the graph is current with
better-code-review-graph graph build --base HEAD --repo-root "<path>". -
Get review context with
better-code-review-graph review context --base HEAD --repo-root "<path>". This returns:- Changed files (auto-detected from git diff)
- Impacted nodes and files (blast radius)
- Source code snippets for changed areas
- Review guidance (test coverage gaps, wide impact warnings, inheritance concerns)
-
Analyze the blast radius by reviewing the
impacted_nodesandimpacted_filesin the JSON result. Focus on:- Functions whose callers changed (may need signature/behavior verification)
- Classes with inheritance changes (Liskov substitution concerns)
- Files with many dependents (high-risk changes)
-
Perform the review using the context. For each changed file:
- Review the source snippet for correctness, style, and potential bugs
- Check if impacted callers/dependents need updates
- Verify test coverage with
better-code-review-graph query query --pattern tests_for --target "<function>" --repo-root "<path>" - Flag any untested changed functions
-
Report findings in a structured format:
## Delta Review ### Summary <One-line overview of the changes> ### Risk Level - **Low**: Test-only changes, documentation, config files - **Medium**: Implementation changes with <5 impacted files, no public API changes - **High**: >5 impacted files OR public API signature/behavior change ### Issues Found - <Bugs, style issues, missing tests> ### Blast Radius - <List of impacted files/functions> ### Recommendations 1. <Actionable suggestion>
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.
- 10d ago First seen · 72 lines · 22 tokens per session scan A 0930aa6ef6d7
review-delta is a skill published in the GitHub repository n24q02m/claude-plugins (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 663 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-08-31.
Other skills, from other repositories
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
phpunit-test-reconciling
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
review-pr
Perform a comprehensive code review of a pull request.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.