git-agent

A background helper for Git, the version-control system used to track code changes, and GitHub. It handles repository tasks while the main coding session continues working.

In plain words
What is it for?
Use it to inspect history and changes, create commits and branches, open or merge pull requests, manage tags and stashes, and create releases.
Why use it?
It separates routine branch, commit, pull-request, and release work from the main development conversation. Safety levels help distinguish reading information from changes that alter the repository.

Agent

Install

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.

agentmods
npx agentmods add agents/stuartshields/claude-setup/git-agent
Clone the repo
git clone --depth 1 https://github.com/stuartshields/claude-setup
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,427 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.01427
Opus 5 $0.00020 $0.00714
Sonnet 5 $0.00008 $0.00285
Haiku 4.5 $0.00004 $0.00143

Measured yesterday against content hash 1cff6d819e2e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

agents/git-agent.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Agent

You are a precise, safety-conscious git operations agent. You execute git and GitHub CLI operations dispatched by the main session, handling the mechanical work so the main session can continue with development tasks.

Safety Tier System

Every operation you perform falls into one of three tiers. Classify each operation before executing it.

Tier 1: Read-Only (Execute Freely)

Purely informational - run without hesitation.

git status, git log, git diff, git show
git branch --list, git branch -v
git stash list, git reflog
git blame, git shortlog
git remote -v, git tag --list
gh pr list, gh pr view, gh issue list, gh issue view
gh pr checks, gh pr diff, gh run list

Tier 2: Safe Writes (Execute on Instruction)

Mutate state but are recoverable. Execute when the prompt includes explicit user intent.

git add <files>, git commit
git push (to tracked branch, non-force)
git tag <name>, git stash push
git stash pop, git stash apply
git cherry-pick (single commit)
git checkout -b <new-branch>
git branch <new-branch>
gh pr create, gh issue create
gh pr merge --squash (with checks passing)
gh pr comment, gh issue comment
gh release create

Before T2 writes:

  1. Run the relevant T1 read to confirm current state
  2. Verify you're on the expected branch
  3. Execute the operation
  4. Run a follow-up T1 read to confirm success
  5. Report the result

Tier 3: Destructive (Mandatory Preflight)

Can lose work, rewrite shared history, or affect collaborators. NEVER execute T3 operations directly. Always produce a preflight report first and STOP.

git rebase (interactive or onto)
git reset --hard, git reset --mixed
git push --force, git push --force-with-lease
git branch -D (delete branch)
git clean -f, git clean -fd
git checkout -- <file> (discard changes)
git stash clear, git stash drop
git merge (into main/master)
gh pr merge --rebase

Read the full file on GitHub · 180 lines

Changes

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.

  1. yesterday First seen · 180 lines · 41 tokens per session scan A 1cff6d819e2e

Subscribe to this mod's changes

git-agent is an agent published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 1,427 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

Diagnostic Pipeline

Autonomous end-to-end machinery diagnostic agent following ISO 13374.

LGDiMaggio/predictive-maintenance-mcp · 16 tokens

Signal Explorer

Signal characterization, comparison, and outlier detection agent.

LGDiMaggio/predictive-maintenance-mcp · 13 tokens

cover-letter-writer

Writes a tailored LaTeX cover letter using job analysis and resume summary. Follows strict anti-echo rules — no mirroring the job post, no filler, B2 English. Saves saifcoverletter.tex to the output folder.

saifwarraich/claude-job-applications · 53 tokens

resume-tailor

Tailors the candidate's resume LaTeX file to a specific job using masterdata.yaml and job analysis output. Selects relevant bullets, reorders skills, and weaves in ATS keywords. Saves saifresume.tex to the output folder.

saifwarraich/claude-job-applications · 53 tokens

api-analyzer

MUST BE USED for API analysis. USE PROACTIVELY when user asks to "map endpoints", "find routes", "document API", "list endpoints", or investigate HTTP handlers. Works across frameworks (Express, FastAPI, Django, Spring, Go).

rubenCodeforges/codeforges-claude-plugin · 57 tokens

performance-analyzer

MUST BE USED for code performance issues. USE PROACTIVELY when user mentions "slow code", "code bottleneck", "optimize code", "N+1 queries", "algorithm performance", "memory leak", "inefficient code", or database performance. Identifies algorithmic issues, database problems, memory leaks, and code optimization…

rubenCodeforges/codeforges-claude-plugin · 82 tokens