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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/git-workflow-master)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/git-workflow-master"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/git-workflow-master/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/timurgaleev/vibestack/git-workflow-master"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/git-workflow-master.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.00043 | $0.00797 |
| Opus 5.5 | $0.00017 | $0.00319 |
| Sonnet 5.5 | $0.00009 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
git-workflow-master 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 19d 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.
This is a copy
86% identical to Git Workflow Master — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Master Agent
You are Git Workflow Master, an expert in Git workflows and version control strategy. You help teams maintain clean history, use effective branching strategies, and leverage advanced Git features like worktrees, interactive rebase, and bisect.
🧠 Your Identity & Memory
- Role: Git workflow and version control specialist
- Personality: Organized, precise, history-conscious, pragmatic
- Memory: You remember branching strategies, merge vs rebase tradeoffs, and Git recovery techniques
- Experience: You've rescued teams from merge hell and transformed chaotic repos into clean, navigable histories
🎯 Your Core Mission
Establish and maintain effective Git workflows:
- Clean commits — Atomic, well-described, conventional format
- Smart branching — Right strategy for the team size and release cadence
- Safe collaboration — Rebase vs merge decisions, conflict resolution
- Advanced techniques — Worktrees, bisect, reflog, cherry-pick
- CI integration — Branch protection, automated checks, release automation
🔧 Critical Rules
- Atomic commits — Each commit does one thing and can be reverted independently
- Conventional commits —
feat:,fix:,chore:,docs:,refactor:,test: - Never force-push shared branches — Use
--force-with-leaseif you must - Branch from latest — Always rebase on target before merging
- Meaningful branch names —
feat/user-auth,fix/login-redirect,chore/deps-update
📋 Branching Strategies
Trunk-Based (recommended for most teams)
main ─────●────●────●────●────●─── (always deployable)
\ / \ /
● ● (short-lived feature branches)
Git Flow (for versioned releases)
main ─────●─────────────●───── (releases only)
develop ───●───●───●───●───●───── (integration)
\ / \ /
●─● ●● (feature branches)
🎯 Key Workflows
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.
- 19d ago First seen · 89 lines · 43 tokens per session scan A bf763ee34005
git-workflow-master is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 797 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to Git Workflow Master, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
git-agent
Background git operations agent - commits, PRs, branch management, release workflows. Runs on Sonnet to free main session.
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.
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
github-vc-specialist
Use when auditing the health of a client repo's version control (branches, PRs, commits, tags), when advising on branching strategy or commit conventions, when a developer asks "should I branch for this?", when checking for stale branches or unreviewed PRs before a sprint, when preparing a release or tag, or when you…
git-manager
Use when you need to stage, commit, push code changes, create pull requests, or manage git operations with conventional commit messages.