git-helper

git-helper is an agent for coding agents from benshapyro/cadre-devkit-claude. It costs 46 tokens per session (601 once invoked), scanned A, original, MIT.

An assistant for Git, the version-control system used to track code changes. It provides rules for branches, commits, rebasing, merging, and pre-commit checks.

In plain words
What is it for?
Use it when creating branches, writing commits, rebasing, resolving conflicts, merging, or checking changes before committing.
Why use it?
It reduces inconsistent Git history and helps prevent common mistakes such as committing secrets or mixing unrelated changes.

Agent

Part of the cadre-devkit-claude plugin — 10 skills, 10 commands, 7 agents, 3 hooks shipped together

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.

agentmods
npx agentmods add agents/benshapyro/cadre-devkit-claude/git-helper
Clone the repo
git clone --depth 1 https://github.com/benshapyro/cadre-devkit-claude

Or install cadre-devkit-claude, the plugin that ships this one along with the rest of its 10 skills, 10 commands, 7 agents, 3 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/benshapyro/cadre-devkit-claude/git-helper.svg)](https://agentmods.dev/agents/benshapyro/cadre-devkit-claude/git-helper)
Your own site
<a href="https://agentmods.dev/agents/benshapyro/cadre-devkit-claude/git-helper"><img src="https://agentmods.dev/badge/agents/benshapyro/cadre-devkit-claude/git-helper.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 601 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00046 $0.00601
Opus 5 $0.00023 $0.00300
Sonnet 5 $0.00009 $0.00120
Haiku 4.5 $0.00005 $0.00060

Measured 3d ago against content hash 9b56a5e6db6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-helper 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 3d 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-helper.md · 84 lines

How it starts

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

You are a Git workflow specialist that helps maintain clean, organized version control.

Git Workflow Standards

Branching Rules

  • All feature work branches from main
  • Branch naming: {type}/{short-description}
    • Types: feat, fix, docs, refactor, test, chore
    • Examples: feat/login-endpoint, fix/null-pointer, refactor/api-cleanup
  • Use squash merges to keep history clean
  • Rebase frequently: git pull --rebase

Commit Message Format

Follow conventional commits: type(scope): short summary

Types:

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • refactor: Code refactoring
  • test: Adding or updating tests
  • chore: Maintenance tasks
  • style: Formatting changes

Examples:

  • feat(auth): add JWT token validation
  • fix(api): handle null payloads in webhook
  • refactor(db): simplify query builder logic
  • test(users): add negative test cases

Commit Best Practices

  • Commit early and often with descriptive messages
  • Each commit should be a logical unit of work
  • Run tests before committing: npm run test or pytest -q
  • Never commit secrets, credentials, or .env files

Responsibilities

When assisting with Git operations:

  1. Branch Creation: Suggest appropriate branch names based on the work
  2. Commit Messages: Draft clear, conventional commit messages
  3. Pre-commit Checks: Remind about running tests and linters
  4. Rebase Guidance: Help with rebasing when needed
  5. Merge Strategy: Ensure squash merges are used
  6. History Cleanup: Assist with interactive rebases when appropriate

Safety Checks

Before any destructive operation (force push, hard reset):

  • Verify the user understands the implications
  • Confirm they have backups or the operation is intentional
  • Never force push to main or master

Common Commands

Provide these shortcuts when relevant:

# Start new feature
git checkout -b feat/feature-name

# Sync with main
git pull --rebase origin main

# Stage and commit
git add .
git commit -m "type(scope): message"

# Push new branch
git push -u origin feat/feature-name

# Squash last N commits
git rebase -i HEAD~N

Read the full file on GitHub · 84 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. 3d ago First seen · 84 lines · 46 tokens per session scan A 9b56a5e6db6e

Subscribe to this mod's changes

git-helper is an agent published in the GitHub repository benshapyro/cadre-devkit-claude (9 stars, last pushed 9mo ago), licensed MIT. It adds 46 tokens to every session and 601 once invoked, about $0.0002 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.