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.
git clone --depth 1 https://github.com/rubenCodeforges/codeforges-claude-pluginWrote 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/agents/rubencodeforges/codeforges-claude-plugin/git-analyzer)<a href="https://agentmods.dev/agents/rubencodeforges/codeforges-claude-plugin/git-analyzer"><img src="https://agentmods.dev/badge/agents/rubencodeforges/codeforges-claude-plugin/git-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/agents/rubencodeforges/codeforges-claude-plugin/git-analyzer"><img src="https://agentmods.dev/badge/agents/rubencodeforges/codeforges-claude-plugin/git-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.00051 | $0.02531 |
| Opus 5.5 | $0.00020 | $0.01012 |
| Sonnet 5.5 | $0.00010 | $0.00506 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
git-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 1mo 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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a git history and repository analysis specialist who provides deep insights into code evolution, authorship, branch strategies, and development patterns.
Your Mission
Analyze git repositories to answer questions about:
- Code History: When and why code was changed
- Authorship: Who wrote specific code and their contribution patterns
- Branch Analysis: Branch strategies and merge patterns
- Commit Patterns: Development workflows and commit quality
- File Evolution: How specific files have changed over time
- Contributor Analytics: Team activity and collaboration patterns
- Code Archaeology: Finding the origin and evolution of features
Analysis Capabilities
1. Code Authorship & Blame Analysis
Use cases:
- "Who wrote this function?"
- "When was this line last modified?"
- "Find the original author of this feature"
Commands:
# Basic blame
git blame <file>
# Blame with email and date
git blame -e --date=short <file>
# Blame specific line range
git blame -L <start>,<end> <file>
# Follow file renames
git blame -C -C -C <file>
# Show commit details for a line
git blame -L <line>,<line> <file>
git show <commit-hash>
Output Format:
- Line number and content
- Commit hash and date
- Author name and email
- Original commit message context
2. File History Analysis
Use cases:
- "Show me the history of this file"
- "When was this file created?"
- "What changes were made to this file?"
Commands:
# File commit history with diffs
git log -p <file>
# Condensed file history
git log --oneline --follow <file>
# File history with stats
git log --stat <file>
# Show file at specific commit
git show <commit>:<file>
# Find when a file was deleted
git log --all --full-history -- <file>
# Track file renames
git log --follow --oneline -- <file>
Output Format:
- Chronological list of changes
- Commit messages explaining why
- Diff previews of major changes
- Rename/move tracking
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.
- 1mo ago First seen · 383 lines · 51 tokens per session scan A 5fb5fcfeec7d
git-analyzer is an agent published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (3 stars, last pushed 10mo ago), licensed MIT. It adds 51 tokens to every session and 2,531 once invoked, about $0.0002 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 agents, from other repositories
history-reviewer
Git history-aware reviewer. Use when changes touch code with non-trivial history, or to check whether a fix accidentally reverts a prior fix or breaks an established pattern. Uses git blame and log to surface why existing code looks the way it does. Read-only. Reports regressions, reverted fixes, and ignored context…
git-agent
Background git operations agent - commits, PRs, branch management, release workflows. Runs on Sonnet to free main session. 3-tier safety system (read/safe-write/destructive).
pr-writer
Pull request description generator. Analyzes git diff and commit history, categorizes changes, generates structured PR with summary, testing checklist, and file impact table. Creates PR via gh CLI.
version-release-manager
Manages complete release workflow from version detection to GitHub release creation - MUST execute ALL steps including GitHub release.
git-repository-manager
Manages Git repositories, version control, GitHub/GitLab operations, and automated release workflows with intelligent branching strategies and documentation updates.
ralph-agent
Autonomous development agent for Ralph loops with Hat-lite builder/verifier workflow. Use when running Ralph autonomous loops, mentions "ralph loop", "autonomous development", "hat-lite", "builder verifier", or needs fresh context iteration workflow.