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/davidvujic/my-eca-config/git-changes-contextnpx skills add DavidVujic/my-eca-config --skill git-changes-contextgit clone --depth 1 https://github.com/DavidVujic/my-eca-configWrote 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/davidvujic/my-eca-config/git-changes-context)<a href="https://agentmods.dev/skills/davidvujic/my-eca-config/git-changes-context"><img src="https://agentmods.dev/badge/skills/davidvujic/my-eca-config/git-changes-context.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 | $0.00051 | $0.00481 |
| Opus 5 | $0.00026 | $0.00241 |
| Sonnet 5 | $0.00010 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
git-changes-context 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 4d 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.
What it actually says
Git Changes Context Skill
Purpose
Provide a deterministic way to obtain the actual change set (unified diff) for use by other agents (code review, security audit, test analysis, etc).
This skill MUST be used whenever a task depends on reviewing changes.
Procedure
Follow these steps strictly and in order.
Important: You MUST attempt every step below until you find a non-empty diff.
Do not return NO_DIFF_FOUND after running only one command.
For each step:
- Run the command exactly as written.
- If the command errors or produces empty output, proceed to the next step.
- If output is non-empty, set
diff_source_commandto the exact command string, setdiff_contextto the raw unified diff, and stop.
Step 1 — Compare against origin/HEAD (preferred default-branch fallback)
Run:
git diff origin/HEAD...HEAD
Step 2 — Compare against origin/main
Run:
git diff origin/main...HEAD
Step 3 — Compare against origin/master
Run:
git diff origin/master...HEAD
Failure Condition
If ALL of the above steps either error or produce empty output:
Return:
diff_source_command = nulldiff_context = ""error = "NO_DIFF_FOUND"
Do not guess. Do not fabricate changes. Do not continue silently.
Output Contract (STRICT)
You MUST return JSON only.
Return exactly this shape:
{ "diff_source_command": string | null, "diff_context": string, "error": string | null }
Rules:
- No commentary.
- No markdown.
- No explanations.
- No additional keys.
diff_contextmust contain raw unified diff text.- If no diff found,
errormust be "NO_DIFF_FOUND".
Guarantees
This skill guarantees:
- Deterministic fallback order
- No hallucinated diffs
- Explicit failure signaling
- Compatibility with strict JSON-only agents
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.
- 4d ago First seen · 100 lines · 51 tokens per session scan A 27b15860d824
git-changes-context is a skill published in the GitHub repository DavidVujic/my-eca-config (11 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 481 once invoked, about $0.0003 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…