git-history-context

An agent that studies a project's Git history, which records how code has changed over time, to provide context for other agents.

In plain words
What is it for?
Use it before code exploration or review to understand recent changes, code churn, and module stability.
Why use it?
It shows which areas change often, which files change together, and which modules may be less stable than their current code suggests.

Agent

Install

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.

agentmods
npx agentmods add agents/reviewtoolkits/code-review-toolkit/git-history-context
Clone the repo
git clone --depth 1 https://github.com/ReviewToolkits/code-review-toolkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,574 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01574
Opus 5 $0.00000 $0.00787
Sonnet 5 $0.00000 $0.00315
Haiku 4.5 $0.00000 $0.00157

Measured 2d ago against content hash 67e086613283, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-history-context 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.

plugins/code-review-toolkit/agents/git-history-context.md · 133 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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.

  1. 2d ago First seen · 133 lines · 0 tokens per session scan A 67e086613283

Subscribe to this mod's changes

git-history-context is an agent published in the GitHub repository ReviewToolkits/code-review-toolkit (6 stars, last pushed 1mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,574 tokens. 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.

Related

Other agents, from other repositories

session-analyzer

Extract tool usage patterns, rework indicators, and context snippets from session JSONL files.

jongwony/epistemic-protocols · 22 tokens

ba-designer

Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.

Arch1eSUN/Arcgentic · 53 tokens

ac-claim-verifier

Phase 3.4 claim verifier. Checks the shipped code against each in-scope acceptance criterion's literal claim from the diff and the current tree, in a fresh context, and EXECUTES NOTHING (no verification command, no single-flight). For a verification-command criterion it reads the command's SOURCE and checks each…

The01Geek/prflow · 155 tokens

silent-failure-hunter

PRFlow's silent-failure reviewer, dispatched by the review engine and available directly. Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk…

The01Geek/prflow · 95 tokens

comment-analyzer

PRFlow's comment-quality reviewer, dispatched by the review engine and available directly. Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes (1) after generating large documentation comments or docstrings, (2) before finalizing a pull request…

The01Geek/prflow · 117 tokens

challenger

Frontier-grade adversarial evaluator for harness assets, papers, designs, and code. Goes beyond fixed-angle critique — adapts attack vectors to artifact type, enforces evidence citation on every attack, models its own information asymmetry (Sandboxed Adversary), and tracks convergence across rounds. Returns structured…

chrono-meta/forge-harness · 102 tokens