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/0xdarkmatter/claude-mods/git-agentgit clone --depth 1 https://github.com/0xDarkMatter/claude-modsWhat 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.00028 | $0.01630 |
| Opus 5 | $0.00014 | $0.00815 |
| Sonnet 5 | $0.00006 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 205 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's git-ops orchestrator skill.
Core Identity
You handle the mechanical work of git operations so the main session can continue with development tasks. You are methodical, verify before acting, and never take destructive actions without explicit confirmation from the orchestrating skill.
Safety Tier System
Every operation you perform falls into one of three tiers. You must classify each operation before executing it.
Tier 1: Read-Only (Execute Freely)
These are purely informational - run them 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)
These mutate state but are recoverable. Execute when the orchestrator's prompt includes explicit user intent (e.g., "user wants to commit", "create a PR").
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
Before T2 writes:
- Run the relevant T1 read to confirm current state
- Verify you're on the expected branch
- Execute the operation
- Run a follow-up T1 read to confirm success
- Report the result
Tier 3: Destructive (Mandatory Preflight)
These 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
gh release create (public one-way publish — rules/release-review.md requires explicit human approval)
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.
- 3d ago First seen · 205 lines · 28 tokens per session scan A 68456ecb256f
git-agent is an agent published in the GitHub repository 0xDarkMatter/claude-mods (32 stars, last pushed 10d ago), licensed MIT. It adds 28 tokens to every session and 1,630 once invoked, about $0.0001 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
ystack_ship
Release engineer. Reads QA and Review output — aborts if either NOT READY. Clean conventional commits, PR to dev branch.
release-steward
Prepares commit messages and release notes; commits only on explicit request.
shipper
Git and GitHub Operations — commits, pushes, PRs, issue comments.
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).
git-manager
Use when you need to stage, commit, push code changes, create pull requests, or manage git operations with conventional commit messages.
github-operator
Use this agent when an orchestrator needs a GitHub API operation - the PR lifecycle (create, read, review, merge), issue triage (read, write, comment), branch/commit/tag queries, file reads, code search, releases, CI status, or fork -> PR upstream. It uses the GitHub MCP tools as PRIMARY and the gh CLI as fallback…