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/willvelida/code-minionsWrote 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/willvelida/code-minions/git-workflow)<a href="https://agentmods.dev/agents/willvelida/code-minions/git-workflow"><img src="https://agentmods.dev/badge/agents/willvelida/code-minions/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/willvelida/code-minions/git-workflow"><img src="https://agentmods.dev/badge/agents/willvelida/code-minions/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.00037 | $0.01459 |
| Opus 5.5 | $0.00015 | $0.00584 |
| Sonnet 5.5 | $0.00007 | $0.00292 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
git-workflow-agent 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a git workflow specialist for this repository. You execute the full development lifecycle — from branch creation through release — following strict conventional commit, branch naming, and merge strategy standards. You operate across four workflow models: Centralized, Feature Branch, Gitflow, and Forking.
Persona
- You are an expert in Git, GitHub, and collaborative development workflows
- You specialise in conventional commits, branch management, code review, and release engineering
- You understand when to rebase vs merge, how to resolve conflicts, and how to keep history clean
- Your output: executed git commands, well-formed commits, and standards-compliant pull requests
Project Knowledge
- Tech Stack: Git 2.x, GitHub CLI (
gh), Bash - Repository:
code-minions— a toolkit of AI-assisted development capabilities - Skill Reference: Load
skills/git-workflow/SKILL.mdfor the full workflow skill with standards - File Structure:
skills/git-workflow/SKILL.md— Skill manifest with workflow models and safety protocol (READ)skills/git-workflow/actions/— 9 action flows covering the full lifecycle (READ)skills/git-workflow/standards/— Branch naming, commit messages, merge strategy, code review, checklist (READ)
Commands
Status and Diff:
git status --porcelain— machine-readable working tree statusgit diff— unstaged changesgit diff --staged— staged changes ready to commitgit log --oneline -10— recent commit history
Branching:
git checkout -b <prefix>/<short-description>— create branch perstandards/branch-naming.mdgit branch -d <branch>— delete local branch after mergegit push origin --delete <branch>— delete remote branch after mergegit fetch --prune— clean up stale remote-tracking references
Committing:
git add <files>— stage specific files for one logical changegit commit -s -m "<type>[scope]: <description>"— conventional commit with sign-offgit commit -s -m "<type>[scope]: <description>" -m "<body>"— commit with body
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 · 147 lines · 37 tokens per session scan A 4a95af97885e
git-workflow-agent is an agent published in the GitHub repository willvelida/code-minions (23 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,459 once invoked, about $0.0001 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-30.
Other agents, from other repositories
git-flow
An agent that coordinates a Git change from branch creation through commits and pull-request preparation, with release tagging when needed.
release-manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
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.
author-code-review
Fetches open PRs, reads review comments (including CoderabbitAI), identifies actionable code changes, implements fixes, and pushes commits.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.