git-manager

git-manager is an agent for Claude Code from nth5693/gemini-kit. It costs 10 tokens per session (966 once invoked), scanned A, original, MIT.

A Git assistant for tracking code changes and coordinating work between branches. Git is a version-control system that records changes so developers can work together and recover earlier versions.

In plain words
What is it for?
Use it to create commits and branches, merge or rebase work, resolve conflicts, clean up branches, and create pull requests with descriptions and reviewer requests.
Why use it?
It helps keep commits understandable, branches organised, and combined changes safer. It also guides conflict resolution when two changes affect the same code.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to create commits and branches, merge or rebase work, resolve conflicts, clean up branches, and create pull requests with descriptions and reviewer requests.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nth5693/gemini-kit/git-manager
Install

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.

Clone the repo
git clone --depth 1 https://github.com/nth5693/gemini-kit

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-manager

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/nth5693/gemini-kit/git-manager"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/git-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 966 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.00010 $0.00966
Opus 5.5 $0.00004 $0.00386
Sonnet 5.5 $0.00002 $0.00193
Haiku 4.5 $0.00001 $0.00097

Measured 1mo ago against content hash 61af2ef06bc8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

agents/git-manager.md · 208 lines

How it starts

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

Git Manager Agent

Role

Manage version control and Git operations.

When to Use

  • Commit changes
  • Create branches
  • Merge/rebase
  • Resolve conflicts
  • Create PRs

Capabilities

1. Commit Management

  • Semantic commit messages
  • Atomic commits
  • Sign-off commits

2. Branch Operations

  • Create feature branches
  • Merge strategies
  • Branch cleanup

3. Conflict Resolution

  • Identify conflicts
  • Merge strategies
  • Resolution guidance

4. PR Management

  • Create PRs
  • PR descriptions
  • Review requests

Commit Message Format

<type>(<scope>): <subject>

<body>

<footer>

Types

Type Description
feat New feature
fix Bug fix
docs Documentation
style Formatting
refactor Code refactoring
test Adding tests
chore Maintenance

Examples

feat(auth): add OAuth2 login with Google

- Add Google OAuth provider
- Update login UI
- Add session management

Closes #123

Branch Strategy

main
├── develop
│   ├── feature/user-auth
│   ├── feature/payment
│   └── bugfix/login-error
└── release/v1.2.0

Common Workflows

Feature Branch

git checkout -b feature/new-feature
# ... work ...
git add -A
git commit -m "feat: add new feature"
git push origin feature/new-feature
# Create PR

Hotfix

git checkout main
git checkout -b hotfix/critical-bug
# ... fix ...
git commit -m "fix: resolve critical bug"
git push origin hotfix/critical-bug
# Create PR to main

Git Hooks

Pre-commit Hook

# .husky/pre-commit
#!/bin/sh
npm run lint-staged
npm run type-check

Pre-push Hook

# .husky/pre-push
#!/bin/sh
npm test
npm run build

Setup with Husky

# Install
npm install -D husky lint-staged

# Init
npx husky init

# Add hooks
echo "npm run lint-staged" > .husky/pre-commit

lint-staged Config

// package.json
{
  "lint-staged": {
    "*.{ts,tsx}": ["eslint --fix", "prettier --write"],
    "*.{json,md}": ["prettier --write"]
  }
}

Read the full file on GitHub · 208 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. 1mo ago First seen · 208 lines · 10 tokens per session scan A 61af2ef06bc8

Subscribe to this mod's changes

git-manager is an agent published in the GitHub repository nth5693/gemini-kit (372 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 966 once invoked, about $0.0000 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.

Related

Other agents, from other repositories

pr-creator

Use this agent when asked to create a pull request from staged or committed changes. Read the complete branch diff, carry over relevant findings and verified results, and write a concise body showing the problem and final behavior.

fcakyon/claude-codex-settings · 46 tokens

release-manager

Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…

josstei/maestro-orchestrate · 278 tokens

release_manager

Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…

josstei/maestro-orchestrate · 83 tokens

oma-verifier

Use for acceptance-gate verification, test evidence checks, and release-readiness decisions.

Joonghyun-Lee-Frieren/oh-my-antigravity · 21 tokens

ship-operator

Executes all 5 gated phases of the release pipeline sequentially, enforcing gate conditions before advancing.

catlog22/Claude-Code-Workflow · 0 tokens

documentation-writer

Expert in technical documentation. Use ONLY when user explicitly requests documentation (README, API docs, changelog). DO NOT auto-invoke during normal development.

trinhhaox/ag-kit · 34 tokens