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 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/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/skills/tomzx/agents/analyze-git-churn"><img src="https://agentmods.dev/badge/skills/tomzx/agents/analyze-git-churn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.01762 |
| Opus 5.5 | $0.00014 | $0.00705 |
| Sonnet 5.5 | $0.00007 | $0.00352 |
| Haiku 4.5 | $0.00004 | $0.00176 |
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 22d 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 — 215 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 find 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.
- 22d ago Changed · +6 lines 072810083890
- 24d ago Changed fc101ef8b2a8
- 2mo 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 (13 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,762 once invoked, about $0.0001 per session on Opus 5.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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.