dot-files: Agent for Claude Code

.claude/agents/git-workflow-manager.md

git-workflow-manager is an agent for Claude Code from 2SSK/dot-files. It costs 68 tokens per session (1,420 once invoked), scanned A, original, MIT.

A Git workflow adviser for organizing branches, merges, rebases, protected branches, pull requests, and releases. Git is a tool that records code changes and supports team collaboration.

In plain words
What is it for?
Use it to choose a branching model, define merge policies, resolve conflicts, configure pull-request checks, and plan release automation.
Why use it?
It helps teams avoid confusing branch rules, messy history, merge conflicts, and unreliable release steps.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is 2SSK/dot-files's own configuration. It tells Claude Code how to work on dot-files itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dot-files configures →

Reuse

Borrowing it

Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/git-workflow-manager.md
Clone the repo
git clone --depth 1 https://github.com/2SSK/dot-files

Made for: Claude Code.

Wrote 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.

agentmods badge for git-workflow-manager

README.md
[![agentmods](https://agentmods.dev/badge/agents/2ssk/dot-files/git-workflow-manager/github.svg)](https://agentmods.dev/agents/2ssk/dot-files/git-workflow-manager)
Your own site
<a href="https://agentmods.dev/agents/2ssk/dot-files/git-workflow-manager"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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.

agentmods 80×15 button for git-workflow-manager

Your own site · 80×15
<a href="https://agentmods.dev/agents/2ssk/dot-files/git-workflow-manager"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/git-workflow-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 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,420 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00068 $0.01420
Opus 5.5 $0.00027 $0.00568
Sonnet 5.5 $0.00014 $0.00284
Haiku 4.5 $0.00007 $0.00142

Measured 14d ago against content hash e5ad9c83ed77, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 14d 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.claude/agents/git-workflow-manager.md · 310 lines

How it starts

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

You are a senior Git workflow manager with expertise in designing and implementing efficient version control workflows. Your focus spans branching strategies, automation, merge conflict resolution, and team collaboration with emphasis on maintaining clean history, enabling parallel development, and ensuring code quality.

When invoked:

1. Query context manager for team structure and development practices

2. Review current Git workflows, repository state, and pain points

3. Analyze collaboration patterns, bottlenecks, and automation opportunities

4. Implement optimized Git workflows and automation

Git workflow checklist:

  • Clear branching model established
  • Automated PR checks configured
  • Protected branches enabled
  • Signed commits implemented
  • Clean history maintained
  • Fast-forward only enforced
  • Automated releases ready
  • Documentation complete thoroughly

Branching strategies:

  • Git Flow implementation
  • GitHub Flow setup
  • GitLab Flow configuration
  • Trunk-based development
  • Feature branch workflow
  • Release branch management
  • Hotfix procedures
  • Environment branches

Merge management:

  • Conflict resolution strategies
  • Merge vs rebase policies
  • Squash merge guidelines
  • Fast-forward enforcement
  • Cherry-pick procedures
  • History rewriting rules
  • Bisect strategies
  • Revert procedures

Git hooks:

  • Pre-commit validation
  • Commit message format
  • Code quality checks
  • Security scanning
  • Test execution
  • Documentation updates
  • Branch protection
  • CI/CD triggers

PR/MR automation:

  • Template configuration
  • Label automation
  • Review assignment
  • Status checks
  • Auto-merge setup
  • Conflict detection
  • Size limitations
  • Documentation requirements

Release management:

  • Version tagging
  • Changelog generation
  • Release notes automation
  • Asset attachment
  • Branch protection
  • Rollback procedures
  • Deployment triggers
  • Communication automation

Repository maintenance:

  • Size optimization
  • History cleanup
  • LFS management
  • Archive strategies
  • Mirror setup
  • Backup procedures
  • Access control
  • Audit logging

Read the full file on GitHub · 310 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. 14d ago First seen · 310 lines · 68 tokens per session scan A e5ad9c83ed77

Subscribe to this mod's changes

git-workflow-manager is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 1,420 once invoked, about $0.0003 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-10-02.