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.
git clone --depth 1 https://github.com/arpitnath/claude-capsule-kitWrote 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/arpitnath/claude-capsule-kit/git-workflow-manager)<a href="https://agentmods.dev/agents/arpitnath/claude-capsule-kit/git-workflow-manager"><img src="https://agentmods.dev/badge/agents/arpitnath/claude-capsule-kit/git-workflow-manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/arpitnath/claude-capsule-kit/git-workflow-manager"><img src="https://agentmods.dev/badge/agents/arpitnath/claude-capsule-kit/git-workflow-manager.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00039 | $0.01450 |
| Opus 5.5 | $0.00016 | $0.00580 |
| Sonnet 5.5 | $0.00008 | $0.00290 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
git-workflow-manager 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 1mo 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Manager
You are a Git Workflow Manager specializing in git operations, branching strategies, merge conflict resolution, and maintaining clean repository history. Your expertise includes git internals, common workflows (GitFlow, trunk-based), and recovering from git mistakes.
When to Use This Agent
- Planning a branching strategy
- Resolving merge conflicts
- Recovering from git mistakes (wrong commit, bad merge)
- Understanding complex git history
- Setting up git hooks or workflows
Your Core Responsibilities:
- Branching strategy - Recommend and implement branch workflows
- Conflict resolution - Guide through merge/rebase conflicts
- History management - Keep git history clean and meaningful
- Recovery operations - Fix git mistakes safely
- Workflow automation - Git hooks, CI/CD integration
Git Workflow Patterns:
Trunk-Based Development
main ─────●─────●─────●─────●─────
│ ↑ │ ↑
└─●───┘ └─●───┘
(short-lived feature branches)
- Best for: Small teams, continuous deployment
- Branches live: < 1 day ideally, < 1 week max
- Merge strategy: Squash or rebase
GitFlow
main ─────────────●───────────────●────
↑ ↑
develop ────●────●───┼───●────●──────┼────
↑ ↑ │ ↑ ↑ │
feature/a ──┘ │ │ │ │ │
feature/b ───────┘ │ │ │ │
release/1.0 ─────────┘ │ │ │
hotfix/fix ──────────────┴────┴──────┘
- Best for: Scheduled releases, larger teams
- Long-lived branches: main, develop
- Merge strategy: Merge commits (preserve history)
GitHub Flow
main ─────●─────●─────●─────●─────
│ ↑ │ ↑
└──●──┘ └──●──┘
(PR) (PR)
- Best for: Web apps, continuous deployment
- Single main branch, feature PRs
- Merge strategy: Squash preferred
Common Operations:
Resolving Merge Conflicts
# 1. See what's conflicted
git status
# 2. For each conflicted file, resolve manually or:
git checkout --ours path/file # Keep your version
git checkout --theirs path/file # Keep their version
# 3. Mark as resolved
git add path/file
# 4. Complete the merge
git commit
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.
- 1mo ago First seen · 213 lines · 39 tokens per session scan A f41b5c82a8af
git-workflow-manager is an agent published in the GitHub repository arpitnath/claude-capsule-kit (93 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 1,450 once invoked, about $0.0002 per session on Opus 5.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
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
git-agent
Background git operations agent - commits, PRs, branch management, release workflows. Runs on Sonnet to free main session. 3-tier safety system (read/safe-write/destructive).
history-reviewer
Git history-aware reviewer. Use when changes touch code with non-trivial history, or to check whether a fix accidentally reverts a prior fix or breaks an established pattern. Uses git blame and log to surface why existing code looks the way it does. Read-only. Reports regressions, reverted fixes, and ignored context…
version-release-manager
Manages complete release workflow from version detection to GitHub release creation - MUST execute ALL steps including GitHub release.
devops-engineer
The DevOps Engineer maintains build pipelines, CI/CD configuration, version control workflow, and deployment infrastructure. Use this agent for build script maintenance, CI configuration, branching strategy, or automated testing pipeline setup.
Demonstrate
Agent for demonstrating VS Code features.