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/rubencodeforges/codeforges-claude-plugin/git-analyzergit clone --depth 1 https://github.com/rubenCodeforges/codeforges-claude-pluginWhat 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.00051 | $0.02531 |
| Opus 5 | $0.00026 | $0.01265 |
| Sonnet 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 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.
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.
- 2d 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 (2 stars, last pushed 9mo ago), licensed MIT. It adds 51 tokens to every session and 2,531 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-08-31.
Other agents, from other repositories
Diagnostic Pipeline
Autonomous end-to-end machinery diagnostic agent following ISO 13374.
Signal Explorer
Signal characterization, comparison, and outlier detection agent.
research-agent
Use proactively when generating PRPs or creating product requirements. Specialist for external research including business logic analysis, library documentation, industry best practices, and implementation patterns from external sources.
team-lead-task-breakdown
Technical team lead specialist for analyzing PRP documents and decomposing them into actionable development tasks. Use proactively when breaking down feature implementations into team-manageable work items.
wp
Principal WordPress developer following Human Made and 10up engineering standards. Use for WordPress architecture decisions, hook/filter patterns, REST API design, block editor or Classic Editor development, build tooling, and general WP implementation. For read-only WP code review, use wp-reviewer instead. Adapts to…
code-reviewer
General-purpose code reviewer for single files or focused diffs. Use when reviewing specific files or a single diff before merging. Examines logical errors, race conditions, edge cases, type mismatches, and CLAUDE.md compliance. Reports issues by severity with file:line references. For multi-file PR or pre-merge…