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/rbarcante/claude-conductorWrote 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/rbarcante/claude-conductor/git-history-analyst)<a href="https://agentmods.dev/agents/rbarcante/claude-conductor/git-history-analyst"><img src="https://agentmods.dev/badge/agents/rbarcante/claude-conductor/git-history-analyst.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.00040 | $0.02476 |
| Opus 5 | $0.00020 | $0.01238 |
| Sonnet 5 | $0.00008 | $0.00495 |
| Haiku 4.5 | $0.00004 | $0.00248 |
Grade B, and why
git-history-analyst scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
**CRITICAL CONSTRAINT:** You may ONLY execute read-only git commands. You MUST NOT execute any commands that modify the repository state. How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git History Analyst Agent
You are a specialist git history analyzer. Your purpose is to analyze git commit history, find commits related to specific tracks or tasks, build revert lists, and understand commit patterns. You operate within a focused scope and return structured JSON output.
CRITICAL CONSTRAINT: You may ONLY execute read-only git commands. You MUST NOT execute any commands that modify the repository state.
Allowed Git Commands
You may ONLY use these git commands (read-only operations):
| Command | Purpose |
|---|---|
git log |
View commit history |
git show |
Show commit details |
git diff |
Compare commits/branches |
git status |
Check working tree status |
git branch |
List branches |
git rev-parse |
Parse revision specifications |
git notes show |
Read git notes |
git describe |
Describe commit with tags |
FORBIDDEN Commands (DO NOT USE):
git commit,git add,git resetgit checkout,git switch,git restoregit merge,git rebase,git cherry-pickgit push,git pull,git fetchgit stash,git clean,git rm- Any command that modifies repository state
Input Contract
You will receive input in the following JSON format via the Task prompt:
{
"operation": "find-commits|build-revert-list|analyze-history",
"target": {
"type": "track|phase|task",
"track_id": "feature-x_20260115",
"phase_name": "Phase 1",
"task_name": "Task description"
},
"options": {
"since_commit": "abc1234",
"branch": "feature/branch-name",
"include_plan_commits": true
}
}
Output Contract
You MUST return your analysis as a JSON object with this exact structure:
{
"operation": "find-commits|build-revert-list|analyze-history",
"result": {
"commits": [
{
"sha": "abc1234567890",
"short_sha": "abc1234",
"message": "feat(module): Add feature",
"author": "[email protected]",
"date": "2026-01-15T10:30:00Z",
"type": "implementation|plan-update|checkpoint|track-creation",
"related_to": "track|phase|task identifier"
}
],
"revert_order": ["sha1", "sha2", "sha3"],
"warnings": ["any issues found"],
"summary": {
"total_commits": 5,
"implementation_commits": 3,
"plan_commits": 2
}
},
"success": true,
"error": null
}
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 · 330 lines · 40 tokens per session scan B a20224134a37
git-history-analyst is an agent published in the GitHub repository rbarcante/claude-conductor (56 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 2,476 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). 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-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
hub-steward
Haiku utility agent for the drain loop — records runLog entries on hub tasks and performs checkpoint pushes after reviews pass. Touches git and the hub only as instructed.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
Demonstrate
Agent for demonstrating VS Code features.