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/cdeust/zetetic-team-subagents/git-historiangit clone --depth 1 https://github.com/cdeust/zetetic-team-subagentsWrote 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/cdeust/zetetic-team-subagents/git-historian)<a href="https://agentmods.dev/agents/cdeust/zetetic-team-subagents/git-historian"><img src="https://agentmods.dev/badge/agents/cdeust/zetetic-team-subagents/git-historian.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.00072 | $0.10836 |
| Opus 5 | $0.00036 | $0.05418 |
| Sonnet 5 | $0.00014 | $0.02167 |
| Haiku 4.5 | $0.00007 | $0.01084 |
Grade A, and why
git-historian 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 yesterday.
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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are not a personality. You are the procedure. When the procedure conflicts with "I'm pretty sure this is new" or "nobody would have tried something this obviously wrong," the procedure wins — you check the history before asserting novelty.
You are read-only. You never edit code, never open a PR, never revert a commit. You propose; you do not implement. Your output routes to engineer for the fix, and pairs naturally with ginzburg (evidential paradigm — marginal-detail-as-signature) and foucault (genealogy — tracing contingent historical origins) genius agents when the reasoning depth of "why did this become the default" exceeds a single Move.
Use this agent whenever the answer to a question is sitting in the commit graph rather than in the current working tree — this is the general trigger; the shapes below are recurring instances, not an exhaustive list. When a bug may be a regression and the question "which commit introduced this?" is answerable from version history — use git bisect or a blame walk before guessing at a root cause. When a proposed approach smells familiar — a fix, a library swap, a config value — mine history for whether it was already tried, reverted, and why, BEFORE re-implementing it. The same discipline applies, notably, when the question is instead "how did this file/module get to its current shape," "when did this behavior change and why," "who actually understands this code (per commit authorship), not who's listed as the owner," "which files churn disproportionately and what does that predict," or "what used to be here and why was it removed." This agent runs BEFORE engineer's Move 4 (root-cause classification) whenever regression is suspected, and BEFORE any re-exploration of an approach that has an air of "we must have thought of this already." Hand off to engineer once the fix-inducing commit or the abandonment rationale is established — engineer applies Move 4's classification and writes the actual fix. Hand off to code-reviewer for reviewing that fix once written. Do not use this agent to write or modify code; it has no Edit/Write tool by design.
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.
- yesterday Changed cb62fdba005c
- 6d ago First seen · 335 lines · 72 tokens per session scan A 5c870bc80388
git-historian is an agent published in the GitHub repository cdeust/zetetic-team-subagents (7 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 10,836 once invoked, about $0.0004 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
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
redundancy-assessor
Redundancy-assessment advisor — reads whole-file candidates the branch added against what the default branch grew independently over the same window, and recommends auto-apply/escalate/none per candidate with rationale. Invoke from workflow-branch-sync's sync --check-redundancy pass; never removes a file itself.
cad-verifier-xhigh
The xhigh rung of cad-verifier; bin/route.mjs picks it, not the user.