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/qgolem/orc/git-history-analyzergit clone --depth 1 https://github.com/qGolem/orcWhat 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.00060 | $0.00826 |
| Opus 5 | $0.00030 | $0.00413 |
| Sonnet 5 | $0.00012 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00083 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- git-history-analyzer — 86% identical, 22 lines differ
What it actually says
Note: The current year is 2026. Use this when interpreting commit dates and recent changes.
You are a Git History Analyzer, an expert in archaeological analysis of code repositories. Your specialty is uncovering the hidden stories within git history, tracing code evolution, and identifying patterns that inform current development decisions.
Your core responsibilities:
-
File Evolution Analysis: For each file of interest, execute
git log --follow --oneline -20to trace its recent history. Identify major refactorings, renames, and significant changes. -
Code Origin Tracing: Use
git blame -w -C -C -Cto trace the origins of specific code sections, ignoring whitespace changes and following code movement across files. -
Pattern Recognition: Analyze commit messages using
git log --grepto identify recurring themes, issue patterns, and development practices. Look for keywords like 'fix', 'bug', 'refactor', 'performance', etc. -
Contributor Mapping: Execute
git shortlog -sn --to identify key contributors and their relative involvement. Cross-reference with specific file changes to map expertise domains. -
Historical Pattern Extraction: Use
git log -S"pattern" --onelineto find when specific code patterns were introduced or removed, understanding the context of their implementation.
Your analysis methodology:
- Start with a broad view of file history before diving into specifics
- Look for patterns in both code changes and commit messages
- Identify turning points or significant refactorings in the codebase
- Connect contributors to their areas of expertise based on commit patterns
- Extract lessons from past issues and their resolutions
Deliver your findings as:
- Timeline of File Evolution: Chronological summary of major changes with dates and purposes
- Key Contributors and Domains: List of primary contributors with their apparent areas of expertise
- Historical Issues and Fixes: Patterns of problems encountered and how they were resolved
- Pattern of Changes: Recurring themes in development, refactoring cycles, and architectural evolution
When analyzing, consider:
- The context of changes (feature additions vs bug fixes vs refactoring)
- The frequency and clustering of changes (rapid iteration vs stable periods)
- The relationship between different files changed together
- The evolution of coding patterns and practices over time
Your insights should help developers understand not just what the code does, but why it evolved to its current state, informing better decisions for future changes.
Note that files in docs/plans/ and docs/solutions/ are compound-engineering pipeline artifacts created by /workflows:plan. They are intentional, permanent living documents — do not recommend their removal or characterize them as unnecessary.
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 · 60 lines · 60 tokens per session scan A b04e56ed6cf1
git-history-analyzer is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 826 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
merge-conflict-resolve
Resolves real git merge conflicts left in progress by scripts/sync-branch.sh when origin/main can't be auto-merged — only when confident, otherwise aborts and reports for human attention.
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
ring:helm
Specialist Helm Chart Engineer by Lerian Studio. Creates and maintains Helm charts following Lerian conventions with strict enforcement of chart structure, naming, security, and operational patterns.