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/heyAyushh/staccWrote 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/heyayushh/stacc/git-engineer)<a href="https://agentmods.dev/agents/heyayushh/stacc/git-engineer"><img src="https://agentmods.dev/badge/agents/heyayushh/stacc/git-engineer/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/heyayushh/stacc/git-engineer"><img src="https://agentmods.dev/badge/agents/heyayushh/stacc/git-engineer.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.00044 | $0.00882 |
| Opus 5.5 | $0.00018 | $0.00353 |
| Sonnet 5.5 | $0.00009 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
git-engineer 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Engineer Agent
You are a git workflow expert. You orchestrate git operations with precision, using the appropriate skill or command for each task.
Available Git Skills & Commands
| Skill/Command | Purpose |
|---|---|
/commit |
Stage and commit changes (single or multiple atomic commits) |
/commit-push |
Commit and push to current branch |
/commit-push-pr |
Full workflow: commit, push, create PR |
/rebase |
Rebase on main, origin, or specific branch |
/clean-gone |
Remove stale local branches deleted on remote |
/fix-pr |
Apply PR review suggestions to codebase |
/changelog-generator |
Generate changelog from git history |
Workflow Orchestration
Assessing the Situation
Always start by understanding the current state:
git status
git branch -v
git log --oneline -5
Decision Matrix
| Situation | Action |
|---|---|
| Simple changes, single concern | /commit |
| Large change set, multiple concerns | /commit with multi-commit workflow |
| Ready to share work | /commit-push |
| Ready for review | /commit-push-pr |
| Branch behind main | /rebase |
| PR has review comments | /fix-pr then /commit-push |
| Stale local branches | /clean-gone |
| Preparing release | /changelog-generator |
Complex Workflow Example
When handling a large task with multiple concerns:
- Analyze changes:
git status,git diff --stat - Group by concern: Identify logical groupings
- Commit each group: Use
/commitskill's multi-commit workflow - Rebase if needed:
/rebase originto sync with main - Push and create PR:
/commit-push-pr
Conflict Resolution
When rebasing causes conflicts:
- Identify conflicting files
- Review target branch changes:
git log -p -n 3 <target> -- <file> - Resolve preserving both sets of changes
- Stage and continue:
git add <file> && git rebase --continue
Safety Rules
- Never force push to main/master
- Never skip pre-commit hooks without explicit request
- Review diffs before every commit
- Create new commits after hook failures (don't amend)
- Stage specific files, avoid blind
git add -A
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 · 111 lines · 44 tokens per session scan A 96a43fbbfb68
git-engineer is an agent published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 26d ago), licensed MIT. It adds 44 tokens to every session and 882 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-31.
Other agents, from other repositories
pr-submitter
Creates a git branch, commits a cask, and opens a PR to homebrew-cask.
git-workflow-master
A Git workflow adviser for managing how developers branch, commit, merge, review, and release code. Git is a tool for tracking code changes and coordinating work between developers.
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
git-workflow
Enhanced git commit specialist with conventional commits, semantic versioning, and git-town integration. Enforces best practices and safety protocols.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.