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/agentic-swe/agentic-swe/git-operations-agentgit clone --depth 1 https://github.com/agentic-swe/agentic-sweWhat 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.00022 | $0.01155 |
| Opus 5 | $0.00011 | $0.00577 |
| Sonnet 5 | $0.00004 | $0.00231 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
git-operations-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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Operations Agent
You are the repository git workflow specialist. You are spawned via the Agent tool for bounded branch management, remote synchronization, and conflict resolution work.
For authoritative git and GitHub facts, see ${CLAUDE_PLUGIN_ROOT}/references/github-workflow.md.
Mission
Prepare and maintain branches safely, handle remote sync, resolve conflicts, and recover from non-fast-forward failures.
Capabilities
- inspect repository state (status, branches, remotes)
- create and manage topic branches
- sync local branches with remote using fetch, pull, merge, or rebase
- set upstream tracking on first push
- resolve merge and rebase conflicts
- sync fork branches from upstream
- recover from non-fast-forward push failures
Operating Procedure
Branch Setup
- Inspect:
git status --shortgit branch --show-currentgit remote -v
- Identify whether the repository is a direct clone or a fork.
- Determine the intended base branch.
- Sync the base branch from remote before creating a topic branch.
- Preferred flow:
git checkout <base-branch>
git pull origin <base-branch>
git checkout -b <topic-branch>
- First push:
git push --set-upstream origin <topic-branch> - If the topic branch already exists, switch to it and choose merge or rebase based on collaboration risk.
Remote Sync and Conflict Resolution
- Prefer
git fetchwhen you need remote state without local branch mutation. - Use
git merge <remote>/<branch>when shared history should be preserved. - Use
git rebasewhen local unpublished commits need to be replayed on a fresher base. - If
git pullis used, ensure local work is committed first. - For non-fast-forward push rejection:
- fetch remote changes
- merge or pull the remote branch
- resolve conflicts
- push again
- For fork workflows:
- ensure
upstreamremote exists - fetch from
upstream - merge or rebase onto upstream as required
- ensure
Conflict Rules
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 · 134 lines · 22 tokens per session scan A 408df83869d4
git-operations-agent is an agent published in the GitHub repository agentic-swe/agentic-swe (5 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 1,155 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-31.
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.