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 skills/timwukp/agent-skills-best-practice/git-workflownpx skills add timwukp/agent-skills-best-practice --skill git-workflowgit clone --depth 1 https://github.com/timwukp/agent-skills-best-practiceWrote 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/skills/timwukp/agent-skills-best-practice/git-workflow)<a href="https://agentmods.dev/skills/timwukp/agent-skills-best-practice/git-workflow"><img src="https://agentmods.dev/badge/skills/timwukp/agent-skills-best-practice/git-workflow.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.1 | $0.00049 | $0.01168 |
| Opus 5 | $0.00024 | $0.00584 |
| Sonnet 5 | $0.00010 | $0.00234 |
| Haiku 4.5 | $0.00005 | $0.00117 |
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 6d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Instructions
Step 1: Identify the Task
Determine which workflow the user needs:
- Commit message - writing or improving a commit message
- Branching strategy - choosing or implementing a branching model
- Conflict resolution - resolving merge conflicts
- Changelog - generating release notes from commit history
Ask clarifying questions only if the intent is ambiguous.
Step 2: Conventional Commits
When writing commit messages, follow the Conventional Commits specification:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types (in order of frequency):
feat- new feature (correlates with MINOR in semver)fix- bug fix (correlates with PATCH in semver)docs- documentation onlystyle- formatting, no code changerefactor- neither fix nor featureperf- performance improvementtest- adding or fixing testschore- build process, tooling, dependenciesci- CI/CD configuration changes
Rules:
- Description is lowercase, no period at end, max 72 characters
- Body wraps at 72 characters, explains what and why (not how)
- Breaking changes: add
!after type orBREAKING CHANGE:in footer
Examples:
feat(auth): add OAuth2 login with Google provider
Implements the OAuth2 authorization code flow for Google.
Stores tokens in encrypted session storage.
Closes #142
fix(api): prevent race condition in concurrent order creation
Added optimistic locking with version column check.
Returns 409 Conflict when version mismatch detected.
Step 3: Branching Strategies
Recommend based on team size and release cadence:
Trunk-Based Development (recommended for most teams):
- Single
mainbranch, always deployable - Short-lived feature branches (max 2 days)
- Feature flags for incomplete work
- Best for: CI/CD, small teams, frequent releases
GitHub Flow:
mainbranch + feature branches- PR-based review before merge
- Deploy from
mainafter merge - Best for: open source, SaaS with continuous deployment
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 176 lines · 49 tokens per session scan A c7751180b2d4
git-workflow is a skill published in the GitHub repository timwukp/agent-skills-best-practice (10 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 1,168 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 skills, from other repositories
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
git-workflow
Git 工作流专家。规范化版本控制，确保提交历史清晰可追溯。支持 Conventional Commits 规范、Pull Request 最佳实践、分支管理策略和自动化工作流。.
changelog
Use when writing a changelog or release notes. Covers what belongs in one, writing for users rather than for git, semantic versioning, and documenting breaking changes so nobody is surprised.
git-workflow
Use for branching, committing, history repair, and release hygiene. Covers atomic commits, rebase versus merge, bisect, reflog recovery, and undoing mistakes safely.
git
Granular git operations with conventional commits - stage, commit, push, PR, merge. Auto-splits commits by type/scope, blocks on secrets, delegates verbose work to git-manager subagent. GitHub CLI conventions: --body-file for PR bodies, treat gh pr checks exit 8 (pending) as retry not failure, guard run-id assignment…
github-cli
Skill "github-cli" from juan294/cc-rpi, covering github cli, json field discovery, pr check interpretation, release vs pr flags and label and merge settings.