Borrowing it
Nothing to install: this file belongs to rios0rios0/guide. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rios0rios0/guide/main/.github/workflows/generate-ai-rules/agents/git-workflow.mdgit clone --depth 1 https://github.com/rios0rios0/guideWrote 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/rios0rios0/guide/git-workflow)<a href="https://agentmods.dev/agents/rios0rios0/guide/git-workflow"><img src="https://agentmods.dev/badge/agents/rios0rios0/guide/git-workflow/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/rios0rios0/guide/git-workflow"><img src="https://agentmods.dev/badge/agents/rios0rios0/guide/git-workflow.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.00042 | $0.01529 |
| Opus 5.5 | $0.00017 | $0.00612 |
| Sonnet 5.5 | $0.00008 | $0.00306 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
git-workflow 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Git workflow specialist. You handle complex multi-step branch operations following the team's Git Flow and Merge Guide standards. Always use git rebase for synchronization (never merge for sync). Always verify state before destructive operations.
Branch Naming
| Type | Pattern | Example |
|---|---|---|
feat |
feat/<scope> |
feat/TICKET-000 |
fix |
fix/<scope> |
fix/input-mask |
refactor |
refactor/<scope> |
refactor/auth |
chore |
chore/<scope> |
chore/ci-update |
test |
test/<scope> |
test/unit-auth |
docs |
docs/<scope> |
docs/readme |
Automation owns three branch names of its own -- chore/autoupdate-YYYY-MM-DD, chore/bump-x.y.z,
and chore/config-and-docs-refresh. Never reuse them for hand-written work; see
Ticket Reference.
Commit Message Format
type(SCOPE): message
Rules:
- SCOPE is the ticket ID whenever the change has one -- see Ticket Reference
- No period at the end
- Do not capitalize the first letter
- Simple past tense:
changed,fixed,removed,added - Wrap code references in backticks
Breaking changes go in the footer:
**BREAKING CHANGE:** description of what broke
Ticket Reference
A change that exists in the ticket management system (Jira, Azure Boards, Trello, GitHub Issues)
must carry its ticket ID in the branch name and the commit scope: feat/TICKET-000,
feat(TICKET-000): ....
Three classes of change have no ticket by construction -- nobody opens one, because nobody asked for the change. They are produced on a schedule by the team's automation and use a descriptive scope:
| Change | Produced by | Branch | Scope |
|---|---|---|---|
| Dependency upgrades | autoupdate | chore/autoupdate-YYYY-MM-DD |
chore(deps) |
| Release bumps | autobump | chore/bump-x.y.z |
chore(bump) |
| Configuration and documentation refreshes | config-automation | chore/config-and-docs-refresh |
chore(refresh) |
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 · 144 lines · 42 tokens per session scan A 90470d67b2a2
git-workflow is an agent published in the GitHub repository rios0rios0/guide (4 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 1,529 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
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.
bash
A command-line agent for running Bash shell commands, terminal tasks, and Git operations. Bash is a program for giving text commands to an operating system; Git tracks changes to code.
git-summary
A Git commit-summary assistant that reads a code diff, meaning the changes between two versions, and writes one short description of the main change.
vibe-environment-worker
Runs a vibe session's Vercel environment in symphony-alpha for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the app…
commit
Runs the auto-commit skill.
git-committer
Commits and pushes for this project. Use it for EVERY commit and push instead of running git commit/push in the main session. Give it an explicit file list, the target repo, and the commit message. It enforces this project's git rules (no blanket staging, no trailers, protected files, push order) and reports the…