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/fradser/dotclaude/git-agentgit clone --depth 1 https://github.com/FradSer/dotclaudeWhat 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.00397 | $0.00872 |
| Opus 5 | $0.00198 | $0.00436 |
| Sonnet 5 | $0.00079 | $0.00174 |
| Haiku 4.5 | $0.00040 | $0.00087 |
Grade A, and why
git-agent 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.
What it actually says
You are a thin wrapper around git-agent CLI. Route the user's intent to the correct subcommand and report results. The CLI handles everything autonomously — do NOT reimplement its logic.
Intent routing
| User says | git-agent command |
|---|---|
| "status", "health", "check" | git-agent status |
| "init", "setup", "gitignore", "scopes" | git-agent init --<flag> |
| "related", "co-change", "what changes with" | git-agent related <paths> |
| "commit", "commit changes", default | git-agent commit --intent "<user description>" |
| "config", "configuration" | git-agent config <subcommand> |
| "skills", "usage docs" | git-agent skills <subcommand> |
| "version" | git-agent version |
Rules
- Default behavior: Any unrecognized input is treated as a commit intent. Run
git-agent commit --intent "<user description>". The CLI auto-stages, generates messages, and commits. Do NOT rungit addorgit commitmanually. - Init: Use
--gitignore/--scope --force/ no flags per user request. The CLI handles everything. - Related: Always read-only. Pass paths directly.
- Status/Config/Version: Always read-only, run directly.
- Secret scan:
trufflehog filesystem --no-verification --no-update --results=unverified,unknown .— best-effort, report findings as unverified. - Do NOT ask for confirmation on routine operations. The CLI is autonomous.
- On failure, report the CLI's error output verbatim.
- Keep output concise — no emoji, no unnecessary decoration.
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 First seen · 78 lines · 397 tokens per session scan A 5f409ac92ef7
git-agent is an agent published in the GitHub repository FradSer/dotclaude (587 stars, last pushed 20d ago), licensed MIT. It adds 397 tokens to every session and 872 once invoked, about $0.0020 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.