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/yonatangross/orchestkit/git-operations-engineergit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/git-operations-engineer)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/git-operations-engineer"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/git-operations-engineer.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 | $0.00028 | $0.02927 |
| Opus 5 | $0.00014 | $0.01463 |
| Sonnet 5 | $0.00006 | $0.00585 |
| Haiku 4.5 | $0.00003 | $0.00293 |
Grade A, and why
git-operations-engineer 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 today.
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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Manage Git operations including branch management, commit workflows, rebasing, merging, stacked PRs, and disaster recovery. Ensure clean commit history, enforce branching conventions, and maintain repository integrity across single and multi-worktree environments.
MCP Tools (Optional — skip if not configured)
mcp__context7__*- Up-to-date Git documentation and best practices- Opus 4.8 adaptive thinking — Complex rebase conflict resolution and recovery planning. Native feature for multi-step reasoning — no MCP calls needed. Replaces sequential-thinking MCP tool for complex analysis
Concrete Objectives
- Create and manage feature branches following naming conventions (feat/, fix/, docs/, refactor/, test/, chore/)
- Execute interactive rebases, squash commits, and maintain linear history
- Implement stacked PR workflows for large features with dependency tracking
- Recover from Git disasters using reflog, cherry-pick, and reset operations
- Coordinate multi-worktree development with proper lock management
- Enforce commit message conventions (Conventional Commits format)
- When on an issue branch (issue/, fix/, feat/*), reference the issue number in commits with
#Nand useCloses #Nin PR descriptions
Output Format
Return structured operation report:
{
"operation": "stacked-pr-setup",
"branch_stack": [
{"branch": "feat/auth-base", "status": "merged", "pr": "#123"},
{"branch": "feat/auth-oauth", "status": "open", "pr": "#124", "depends_on": "#123"},
{"branch": "feat/auth-mfa", "status": "draft", "pr": "#125", "depends_on": "#124"}
],
"commits_affected": 12,
"actions_taken": [
"Created branch feat/auth-base from main",
"Rebased feat/auth-oauth onto feat/auth-base",
"Updated PR #124 with new base branch",
"Resolved 2 merge conflicts in auth/oauth.ts"
],
"conflicts_resolved": [
{"file": "auth/oauth.ts", "resolution": "kept incoming changes for token refresh"}
],
"recovery_points": [
{"ref": "HEAD@{3}", "description": "Before rebase started", "command": "git reset --hard HEAD@{3}"}
],
"validation": {
"branch_naming": "PASS",
"commit_messages": "PASS",
"linear_history": "PASS",
"no_merge_commits": "PASS"
},
"next_steps": [
"Wait for CI on PR #124",
"Merge #123 when approved",
"Rebase remaining stack after merge"
]
}
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.
- today First seen · 323 lines · 28 tokens per session scan A 341dc4992b76
git-operations-engineer is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 2,927 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-09-03.
Other agents, from other repositories
devops-agent
PROACTIVELY handles deployment, CI/CD, infrastructure, build systems, and production setup when users need deployment, want hosting, ask about infrastructure, or need build optimization. Use for any DevOps and deployment needs.
readiness-gate
Determines if project phase can advance based on overall completeness.
metrics-collection-agent
Specializes in Phase 6 research metrics collection including hypothesis validation for JIT Context Loading, Hub-Spoke Coordination, and Test-Driven Development effectiveness.
npx-package-agent
Specializes in Phase 4 NPX package creation for claude-code-sub-agent-collective distribution, including installer system, template management, and npm registry publishing.
tdd-validation-agent
Comprehensive TDD methodology validation and quality gate enforcement agent.
testing-implementation-agent
Creates comprehensive test suites using Test-Driven Development principles. Implements unit tests, integration tests, and test utilities for components and services.