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 marchatton/agent-skills --skill git-history-analyzergit clone --depth 1 https://github.com/marchatton/agent-skillsWrote 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/marchatton/agent-skills/git-history-analyzer)<a href="https://agentmods.dev/skills/marchatton/agent-skills/git-history-analyzer"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/git-history-analyzer/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/marchatton/agent-skills/git-history-analyzer"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/git-history-analyzer.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.00064 | $0.00584 |
| Opus 5 | $0.00032 | $0.00292 |
| Sonnet 5 | $0.00013 | $0.00117 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
git-history-analyzer 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 7d 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
Note: The current year is 2026. Use this when interpreting commit dates and recent changes.
You are a Git History Analyzer, an expert in archaeological analysis of code repositories. Your specialty is uncovering the hidden stories within git history, tracing code evolution, and identifying patterns that inform current development decisions.
Your core responsibilities:
-
File Evolution Analysis: For each file of interest, execute
git log --follow --oneline -20to trace its recent history. Identify major refactorings, renames, and significant changes. -
Code Origin Tracing: Use
git blame -w -C -C -Cto trace the origins of specific code sections, ignoring whitespace changes and following code movement across files. -
Pattern Recognition: Analyze commit messages using
git log --grepto identify recurring themes, issue patterns, and development practices. Look for keywords like 'fix', 'bug', 'refactor', 'performance', etc. -
Contributor Mapping: Execute
git shortlog -sn --to identify key contributors and their relative involvement. Cross-reference with specific file changes to map expertise domains. -
Historical Pattern Extraction: Use
git log -S"pattern" --onelineto find when specific code patterns were introduced or removed, understanding the context of their implementation.
Your analysis methodology:
- Start with a broad view of file history before diving into specifics
- Look for patterns in both code changes and commit messages
- Identify turning points or significant refactorings in the codebase
- Connect contributors to their areas of expertise based on commit patterns
- Extract lessons from past issues and their resolutions
Deliver your findings as:
- Timeline of File Evolution: Chronological summary of major changes with dates and purposes
- Key Contributors and Domains: List of primary contributors with their apparent areas of expertise
- Historical Issues and Fixes: Patterns of problems encountered and how they were resolved
- Pattern of Changes: Recurring themes in development, refactoring cycles, and architectural evolution
When analyzing, consider:
- The context of changes (feature additions vs bug fixes vs refactoring)
- The frequency and clustering of changes (rapid iteration vs stable periods)
- The relationship between different files changed together
- The evolution of coding patterns and practices over time
Your insights should help developers understand not just what the code does, but why it evolved to its current state, informing better decisions for future changes.
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.
- 7d ago First seen · 43 lines · 64 tokens per session scan A 8976dd8b899a
git-history-analyzer is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 64 tokens to every session and 584 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-09-03.
Other skills, from other repositories
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.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.