Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/felvieira/claude-skills-fvnpx agentmods add commands/felvieira/claude-skills-fv/diff-impactWrote 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/commands/felvieira/claude-skills-fv/diff-impact)<a href="https://agentmods.dev/commands/felvieira/claude-skills-fv/diff-impact"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/diff-impact/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/commands/felvieira/claude-skills-fv/diff-impact"><img src="https://agentmods.dev/badge/commands/felvieira/claude-skills-fv/diff-impact.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.00119 | $0.01233 |
| Opus 5 | $0.00060 | $0.00616 |
| Sonnet 5 | $0.00024 | $0.00247 |
| Haiku 4.5 | $0.00012 | $0.00123 |
Grade A, and why
diff-impact 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 11d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/diff-impact — Ripple analysis antes do merge
Cruza git diff com graphify-out/graph.json pra responder: se eu mergear isso agora, o que mais pode quebrar?
Inspirado em /understand-diff do Lum1104/Understand-Anything (MIT). Implementação própria — zero-dep Node, usa o graphify-out/ já existente.
Quando usar
- Antes de abrir PR — saber se a mudança é local ou cross-cutting
- Durante review final (skill 11) — confirmar que o reviewer olhou todos os pontos afetados
- Após refactor — validar que ripple ficou contido
- Em legacy — antes de tocar um módulo godzilla, ver quem mais depende dele
Quando NÃO usar
- Repo sem
graphify-out/graph.json(rodegraphify update .antes) - Mudança em arquivo não-código (markdown, JSON, configs) — graphify só indexa código
- Hot-fix urgente que não pode esperar análise
Modos
# vs HEAD~1 (último commit)
node scripts/diff-impact.mjs
# vs staged (antes de commit)
node scripts/diff-impact.mjs --staged
# vs branch main
node scripts/diff-impact.mjs --ref main
# ajustar profundidade BFS (default 2)
node scripts/diff-impact.mjs --depth 3
# machine-readable
node scripts/diff-impact.mjs --json
Output esperado
Diff Impact Analysis
========================================================================
Changed files: 3 (matched 3 in graph, unmatched 0)
Directly touched nodes: 7
Dependents in 2 hops (the ripple): 18
Dependencies in 2 hops (what changed code calls): 12
Directly touched:
validateInput() src/lib/validators.ts
parseAuth() src/lib/auth.ts
...
Ripple — who depends on the touched code (depth 2):
hop 1: 11 nodes
- loginHandler src/routes/login.ts
- signupHandler src/routes/signup.ts
...
hop 2: 7 nodes
- resetPasswordRoute src/routes/password.ts
...
Risk Banding
A partir de dependents_count (ripple), 3 faixas qualitativas — ponto de partida a calibrar por projeto, não constantes universais:
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.
- 11d ago First seen · 118 lines · 119 tokens per session scan A 2235bb4cd155
diff-impact is a command published in the GitHub repository felvieira/claude-skills-fv (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 119 tokens to every session and 1,233 once invoked, about $0.0006 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 commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.