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 fatihkan/badi --skill sc-diff-reportgit clone --depth 1 https://github.com/fatihkan/badiWrote 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/fatihkan/badi/sc-diff-report)<a href="https://agentmods.dev/skills/fatihkan/badi/sc-diff-report"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/sc-diff-report.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.00021 | $0.02007 |
| Opus 5 | $0.00010 | $0.01004 |
| Sonnet 5 | $0.00004 | $0.00401 |
| Haiku 4.5 | $0.00002 | $0.00201 |
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 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.
This is a copy
98% identical to sc-diff-report — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 247 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).
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:
- Added files — entirely new files (highest priority)
- Modified files — existing files with changes
- Deleted files — removed files (check for orphaned references)
- 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
generatedmarkers) - Lock files — delegate to sc-dependency-audit pattern matching
- Static assets (images, fonts, CSS) — skip
- Configuration files — keep, high priority for security review
Dependency Change Detection
If lock files or manifests changed:
package.json/package-lock.json— extract added/removed/updated packagesgo.mod/go.sum— extract module changesCargo.toml/Cargo.lock— extract crate changesrequirements.txt/poetry.lock— extract package changes- Flag newly added dependencies for supply chain review
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 First seen · 247 lines · 21 tokens per session scan A 069eb7d36a7a
sc-diff-report is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 2,007 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to sc-diff-report, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
catchup
Restore context after /clear by summarizing recent work and project state.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
committing
Creates quality git commits with conventional commit format. Use when asked to commit changes or create a commit message.
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…
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.