sc-diff-report

sc-diff-report is a skill for Claude Code, Codex from ersinkoc/security-check. It costs 21 tokens per session (2,186 once invoked), scanned A, original, MIT.

A security scan for only the files changed in a Git diff, pull request, or recent commit. A Git diff is the record of changes between versions of a project.

In plain words
What is it for?
Use it to review a pull request, commit, staged changes, or another selected change range. It produces a security report for the changed files.
Why use it?
Scanning just the changed files gives focused feedback during code review and separates newly introduced issues from problems that were already there.

Skill for Claude CodeCodex

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

Good fit Use it to review a pull request, commit, staged changes, or another selected change range. It produces a security report for the changed files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ersinkoc/security-check/sc-diff-report
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 ersinkoc/security-check --skill sc-diff-report
Clone the repo
git clone --depth 1 https://github.com/ersinkoc/security-check

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 sc-diff-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-diff-report/github.svg)](https://agentmods.dev/skills/ersinkoc/security-check/sc-diff-report)
Your own site
<a href="https://agentmods.dev/skills/ersinkoc/security-check/sc-diff-report"><img src="https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-diff-report/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 sc-diff-report

Your own site · 80×15
<a href="https://agentmods.dev/skills/ersinkoc/security-check/sc-diff-report"><img src="https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-diff-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,186 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00021 $0.02186
Opus 5.5 $0.00008 $0.00874
Sonnet 5.5 $0.00004 $0.00437
Haiku 4.5 $0.00002 $0.00219

Measured 1mo ago against content hash 879c5f5b514b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sc-diff-report 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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/sc-diff-report/SKILL.md · 261 lines

How it starts

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

SC: Diff Report — Incremental Security Scan

Purpose

Performs a targeted security scan on only the files changed in a git diff, pull request, or recent commit. This enables fast, focused security feedback during code review without the overhead of a full codebase scan. Classifies findings as "new" (introduced by changes) vs "existing" (pre-existing in touched files).

Diff mode is always partial coverage. Apply the evidence contract in sc-orchestrator: verify causality against the base revision, independently challenge candidates, and never present unresolved or pre-existing leads as newly introduced vulnerabilities.

Activation

Activates when the user issues any of:

  • "scan diff"
  • "scan changes"
  • "PR scan"
  • "scan commit"
  • "incremental scan"

Output

File: security-report/diff-report.md

Phase 1: Change Detection

Git Diff Extraction

Determine the diff scope based on user context:

PR Mode (most common):

git diff main...HEAD --name-only
git diff main...HEAD

Staged changes:

git diff --cached --name-only
git diff --cached

Last commit:

git diff HEAD~1 --name-only
git diff HEAD~1

Custom range:

git diff {base}...{head} --name-only
git diff {base}...{head}

Changed File Inventory

From the diff output, build an inventory:

  1. Added files — entirely new files (highest priority)
  2. Modified files — existing files with changes
  3. Deleted files — removed files (check for orphaned references)
  4. Renamed files — detect renames with content changes

For each changed file, record:

  • File path
  • Change type (added/modified/deleted/renamed)
  • Lines added (line numbers)
  • Lines removed (line numbers)
  • Total change size (lines added + removed)

Change Filtering

Filter out changes unlikely to have security impact:

  • Documentation files (.md, .txt, .rst) — skip unless they contain config
  • Test files — scan but mark as test context
  • Generated files — skip (check for generated markers)
  • Lock files — delegate to sc-dependency-audit pattern matching
  • Static assets (images, fonts, CSS) — skip
  • Configuration files — keep, high priority for security review

Read the full file on GitHub · 261 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. 1mo ago Changed · +13 lines 879c5f5b514b
  2. 1mo ago First seen · 248 lines · 21 tokens per session scan A 7e6f96c7e487

Subscribe to this mod's changes

sc-diff-report is a skill published in the GitHub repository ersinkoc/security-check (83 stars, last pushed 17d ago), licensed MIT. It adds 21 tokens to every session and 2,186 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens