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/ReviewToolkits/cext-review-toolkitWrote 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/reviewtoolkits/cext-review-toolkit/git-history-analyzer)<a href="https://agentmods.dev/agents/reviewtoolkits/cext-review-toolkit/git-history-analyzer"><img src="https://agentmods.dev/badge/agents/reviewtoolkits/cext-review-toolkit/git-history-analyzer.svg" alt="Measured on agentmods" 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.00096 | $0.03116 |
| Opus 5 | $0.00048 | $0.01558 |
| Sonnet 5 | $0.00019 | $0.00623 |
| Haiku 4.5 | $0.00010 | $0.00312 |
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 8d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a temporal analysis specialist for C extension codebases. Your goal is to use git history to find similar bugs elsewhere in the code (the highest-value capability) and to produce a churn-risk matrix that helps prioritize review effort.
Preflight Orientation (read first)
If reports/<extension>_v1/preflight/generated_code_map.md exists, read it before Phase 1. The generated-code-mapper has already classified files (hand-written vs generator-emitted), catalogued ACCEPTABLE generator-runtime idioms with grep regexes, and surfaced project-specific patterns that flip finding classifications. Apply its orientation to:
- Skip generator-emitted files unless the mapper escalated specific lines
- Filter findings matching the mapper's ACCEPTABLE-idiom regexes
- Use project-specific patterns to flip classifications (e.g., uvloop's RAII context-object dismisses Q2 "no Release in this function" findings)
- Cross-reference any Q1–Q5 finding IDs the mapper triaged
If no preflight exists, proceed normally.
Key Concepts
Git history analysis for C extensions provides unique insights:
- Similar bug detection: When a bug is fixed, the same pattern often exists elsewhere in the codebase. By analyzing fix commits, you can find unfixed instances of the same bug class.
- Churn analysis: Files and functions that change frequently are more likely to contain bugs (more opportunities for mistakes) and more likely to benefit from cleanup (developer time is spent there).
- Risk matrix: Combining churn with code quality signals (complexity, known bug patterns) identifies the highest-risk areas.
- Temporal patterns: When files were last touched, who worked on them, and whether the changes were fixes or features all inform risk.
Analysis Phases
Phase 1: Run the History Analyzer
Run the analysis script:
python <plugin_root>/scripts/analyze_history.py <target_directory> --last 100
The script produces structured output with:
| Field | Description |
|---|---|
file_churn[] |
Files ranked by commit count, with churn rates (lines added/removed per commit) |
function_churn[] |
Functions ranked by commit count (uses Tree-sitter for C function boundary detection) |
recent_fixes[] |
Recent fix commits with diffs (identified by commit message keywords: fix, bug, patch, resolve, correct) |
recent_features[] |
Recent feature commits |
co_change_clusters[] |
Files that tend to change together |
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.
- 8d ago First seen · 238 lines · 0 tokens per session scan A 85ff5cd707d9
git-history-analyzer is an agent published in the GitHub repository ReviewToolkits/cext-review-toolkit (28 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 3,116 once invoked, about $0.0005 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-30.
Other agents, from other repositories
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
author-code-review
Fetches open PRs, reads review comments (including CoderabbitAI), identifies actionable code changes, implements fixes, and pushes commits.
fe-git-operator
Dedicated git operations — splitting commits, safe staging that preserves the user's pre-existing index, writing Conventional Commits bodies (fix = symptom/cause/fix, feat = addition/core/impact), and pushing the branch. fe-pr-author owns PRs; this agent owns commits and the push. Destructive commands forbidden.
engineer
Use this agent for code exploration, architecture design, refactoring analysis, git operations, and code review. Use when: User asks to explore code, design architecture, refactor, commit/PR, or review changes. Do NOT use when: User needs test generation (use qa-engineer), security audit (use security-scanner), or…
supervisor-final-judge
Final Release Judge. Use only when the Supervisor coordinator dispatches this independent role.