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/benshapyro/cadre-devkit-claude/git-helpergit clone --depth 1 https://github.com/benshapyro/cadre-devkit-claudeWrote 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/benshapyro/cadre-devkit-claude/git-helper)<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>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.00046 | $0.00601 |
| Opus 5 | $0.00023 | $0.00300 |
| Sonnet 5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
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.
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
- Types:
- 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 featurefix: Bug fixdocs: Documentation changesrefactor: Code refactoringtest: Adding or updating testschore: Maintenance tasksstyle: Formatting changes
Examples:
feat(auth): add JWT token validationfix(api): handle null payloads in webhookrefactor(db): simplify query builder logictest(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 testorpytest -q - Never commit secrets, credentials, or
.envfiles
Responsibilities
When assisting with Git operations:
- Branch Creation: Suggest appropriate branch names based on the work
- Commit Messages: Draft clear, conventional commit messages
- Pre-commit Checks: Remind about running tests and linters
- Rebase Guidance: Help with rebasing when needed
- Merge Strategy: Ensure squash merges are used
- 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
mainormaster
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
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.
- 3d ago First seen · 84 lines · 46 tokens per session scan A 9b56a5e6db6e
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.
Other agents, from other repositories
git-workflow
Agent "git-workflow" from callstack/react-native-testing-library, covering git, releases, and pr workflow, agent git restrictions, commits and releases and pr draft workflow.
pr-submitter
Creates a git branch, commits a cask, and opens a PR to homebrew-cask.
git-workflow-master
Git工作流专家,负责分支策略设计、合并冲突解决、代码历史维护、CI集成和团队Git规范制定.
Git
Unified agent for all git/GitHub operations - issues, PR comments, tech debt, releases.
shipper
Git and GitHub Operations — commits, pushes, PRs, issue comments.
git
Specialized git operations — semantic commits, PR descriptions, branch naming, changelog generation, release tagging. Convention-aware utility replacing ad-hoc git commands.