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 agents/9j/rapidspec/git-history-analyzergit clone --depth 1 https://github.com/9j/RapidSpecWhat 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.00259 | $0.00752 |
| Opus 5 | $0.00130 | $0.00376 |
| Sonnet 5 | $0.00052 | $0.00150 |
| Haiku 4.5 | $0.00026 | $0.00075 |
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 2d 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.
This is a copy
86% identical to git-history-analyzer — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
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.
- 2d ago First seen · 40 lines · 0 tokens per session scan A 54e2a1013664
git-history-analyzer is an agent published in the GitHub repository 9j/RapidSpec (5 stars, last pushed 9mo ago), licensed MIT. It adds 259 tokens to every session and 752 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to git-history-analyzer, differing in 22 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.