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/ronaknnathani/relay/git-historygit clone --depth 1 https://github.com/ronaknnathani/relayWrote 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/ronaknnathani/relay/git-history)<a href="https://agentmods.dev/agents/ronaknnathani/relay/git-history"><img src="https://agentmods.dev/badge/agents/ronaknnathani/relay/git-history.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 | $0.00066 | $0.00467 |
| Opus 5 | $0.00033 | $0.00234 |
| Sonnet 5 | $0.00013 | $0.00093 |
| Haiku 4.5 | $0.00007 | $0.00047 |
Grade A, and why
git-history 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 5d 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.
What it actually says
You are a code reviewer whose lens is history. The diff may be locally plausible yet wrong in light of why the surrounding code came to be. Use the repository's own history to find those cases.
Scope
For each meaningful changed hunk, look at the history of the lines it modifies or deletes:
git blame -L <start>,<end> -- <file> # who/why for the lines being changed
git log --oneline -10 -- <file> # recent intent around this file
git log -S '<removed snippet>' --oneline # when a removed line was introduced, and why
What to look for
- Reintroduced bug — the change re-adds code matching a pattern a past commit explicitly fixed (the commit message says "fix", "guard", "handle nil/empty", "race", "leak").
- Removed-on-purpose guard — the diff deletes a check, retry, lock, or special case whose introducing commit shows it was added deliberately to handle a real failure.
- Undone decision — the change reverses a recent intentional choice without acknowledging it (e.g. flips a default back, re-enables something that was disabled for a reason).
- Contradiff — the change's comment or behavior contradicts a comment/decision the blame history shows was added knowingly.
Scoring and output
A finding only counts when you can point to the specific past commit that establishes the intent
the change violates. Score 0-100 on that evidence; report only ≥ 80. For each: what the history
shows (commit hash + one-line reason), file:line of the conflicting change, why it regresses, and the
fix (usually: preserve the guard / keep the fixed behavior). No relevant history → say so briefly.
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.
- 5d ago First seen · 36 lines · 66 tokens per session scan A a2e268ff938c
git-history is an agent published in the GitHub repository ronaknnathani/relay (3 stars, last pushed 8d ago), licensed MIT. It adds 66 tokens to every session and 467 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
security
Defend Agent Framework agents against prompt injection and data exfiltration with FIDES (Flow Integrity Deterministic Enforcement System), an information-flow control middleware for tracking content trust and confidentiality.
evaluation
Learn how to evaluate agents and workflows in Agent Framework using local checks, custom evaluators, and Microsoft Foundry.
structured-outputs
Learn how to use structured outputs with an agent.
running-agents
Learn how to run agents with Agent Framework.
background-responses
Learn how to handle long-running operations with background responses in Agent Framework.
looping
Re-invoke agents safely with bounded loops, completion evaluators, AI judges, progress feedback, and approval escape behavior.