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/ersinkoc/security-check/sc-diff-reportnpx skills add ersinkoc/security-check --skill sc-diff-reportgit clone --depth 1 https://github.com/ersinkoc/security-checkWhat 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 | $0.00021 | $0.02014 |
| Opus 5 | $0.00010 | $0.01007 |
| Sonnet 5 | $0.00004 | $0.00403 |
| 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 3d 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 — 248 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.
- 3d ago First seen · 248 lines · 21 tokens per session scan A 7e6f96c7e487
sc-diff-report is a skill published in the GitHub repository ersinkoc/security-check (56 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 2,014 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…