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/tomzx/agents/analyze-git-churnnpx skills add tomzx/agents --skill analyze-git-churngit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/analyze-git-churn)<a href="https://agentmods.dev/skills/tomzx/agents/analyze-git-churn"><img src="https://agentmods.dev/badge/skills/tomzx/agents/analyze-git-churn.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.00036 | $0.01767 |
| Opus 5 | $0.00018 | $0.00883 |
| Sonnet 5 | $0.00007 | $0.00353 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
analyze-git-churn 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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TODAY=!date +%Y-%m-%d
Git Churn Analysis
Analyzes the git commit history over a chosen period to surface the files that changed most frequently, then inspects each high-churn file and produces concrete, prioritized improvement suggestions.
Prerequisites
gitrepository with commit history- Working directory is the root of the repository (or a subdirectory of it)
- Optional:
$1— period to analyze:day,week, ormonth(defaults toweek)
Period Mapping
| Argument | --since value |
|---|---|
day |
1 day ago |
week |
1 week ago |
month |
1 month ago |
If $1 is not provided, default to week.
Steps
1. Determine the Analysis Window
Map $1 → a git log --since value using the table above.
2. Collect Churn Data
Run the following to count how many commits touched each file in the window:
git log --since="<period>" --name-only --pretty=format: | sort | uniq -c | sort -rn | head -30
Also capture per-file insertion/deletion totals to measure change volume:
git log --since="<period>" --numstat --pretty=format: | awk 'NF==3 {add[$3]+=$1; del[$3]+=$2; commits[$3]++} END {for (f in commits) printf "%d\t%d\t%d\t%s\n", commits[f], add[f], del[f], f}' | sort -rn | head -30
Exclude files that no longer exist (deleted files are noise). For each candidate path, confirm it still exists:
git ls-files --error-unmatch <path> 2>/dev/null
3. Rank High-Churn Files
Build a ranked table using the commit-count as the primary sort key:
| Rank | File | Commits | Lines Added | Lines Deleted | Net |
|---|---|---|---|---|---|
| 1 | … | N | +X | −Y | Z |
Focus the analysis on the top 10 files. If fewer than 3 files show more than 1 commit, widen the period automatically and note the change.
4. Inspect Each High-Churn File
For each of the top files:
- Read the file contents.
- Review recent commit messages that touched the file:
git log --since="<period>" --oneline -- <path> - Look at the diff for representative recent changes:
git diff HEAD~5 HEAD -- <path>
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 · 209 lines · 36 tokens per session scan A 30e353d6d15d
analyze-git-churn is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,767 once invoked, about $0.0002 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-31.
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…