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/asyrafhussin/agent-skills/git-workflownpx skills add AsyrafHussin/agent-skills --skill git-workflowgit clone --depth 1 https://github.com/AsyrafHussin/agent-skillsWrote 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/asyrafhussin/agent-skills/git-workflow)<a href="https://agentmods.dev/skills/asyrafhussin/agent-skills/git-workflow"><img src="https://agentmods.dev/badge/skills/asyrafhussin/agent-skills/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 | $0.00059 | $0.03143 |
| Opus 5 | $0.00030 | $0.01571 |
| Sonnet 5 | $0.00012 | $0.00629 |
| Haiku 4.5 | $0.00006 | $0.00314 |
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 5d 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 — 562 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Git best practices, commit conventions, branching strategies, and pull request workflows. Guidelines for maintaining a clean, useful git history.
When to Apply
Reference these guidelines when:
- Writing commit messages
- Creating branches
- Setting up git workflows
- Reviewing pull requests
- Maintaining git history
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Commit Messages | CRITICAL | commit- |
| 2 | Branching Strategy | HIGH | branch- |
| 3 | Pull Requests | HIGH | pr- |
| 4 | History Management | MEDIUM | history- |
| 5 | Collaboration | MEDIUM | collab- |
Quick Reference
1. Commit Messages (CRITICAL)
commit-conventional- Use conventional commitscommit-atomic- Atomic commits (one logical change)commit-present-tense- Use imperative present tensecommit-meaningful- Descriptive, meaningful messagescommit-body- Add body for complex changescommit-references- Reference issues/ticketscommit-git-hooks- Enforce standards with Husky + commitlint
2. Branching Strategy (HIGH)
branch-naming- Consistent branch namingbranch-feature- Feature branch workflowbranch-main-protected- Protect main branchbranch-short-lived- Keep branches short-livedbranch-delete-merged- Delete merged branchesbranch-release- Release branch strategybranch-workflow-strategies- GitFlow vs GitHub Flow vs Trunk-Basedbranch-monorepo- Monorepo git workflows
3. Pull Requests (HIGH)
pr-small- Keep PRs small and focusedpr-description- Write clear descriptionspr-reviewers- Request appropriate reviewerspr-ci-pass- Ensure CI passespr-squash- Squash when appropriatepr-draft- Use draft PRs for WIP and early feedback
4. History Management (MEDIUM)
history-rebase- Rebase vs mergehistory-no-force-push- Avoid force push to shared brancheshistory-clean- Keep history cleanhistory-tags- Use tags for releaseshistory-worktree- Work on multiple branches with git worktree
What ships with it
36 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.
- AGENTS.md 5.5 KB
- metadata.json 6.6 KB
- README.md 2.3 KB
- rules/_sections.md 3.7 KB
- rules/_template.md 3.2 KB
- rules/branch-delete-merged.md 2.8 KB
- rules/branch-feature-workflow.md 2.5 KB
- rules/branch-main-protected.md 2.4 KB
- rules/branch-monorepo.md 3.2 KB
- rules/branch-naming-convention.md 2.4 KB
- rules/branch-release-strategy.md 3.1 KB
- rules/branch-short-lived.md 2.7 KB
- rules/branch-workflow-strategies.md 3.1 KB
- rules/collab-code-review.md 3.4 KB
- rules/collab-communication.md 3.9 KB
- rules/collab-conflict-resolution.md 3.4 KB
- rules/collab-gitignore.md 2.8 KB
- rules/commit-atomic-changes.md 2.1 KB
- rules/commit-body-context.md 2.9 KB
- rules/commit-breaking-changes.md 3.3 KB
- rules/commit-conventional-format.md 2.0 KB
- rules/commit-git-hooks.md 2.8 KB
- rules/commit-imperative-mood.md 2.2 KB
- rules/commit-meaningful-subject.md 2.4 KB
- rules/commit-references.md 2.5 KB
- rules/history-clean-commits.md 3.0 KB
- rules/history-no-force-push.md 3.0 KB
- rules/history-rebase-vs-merge.md 2.8 KB
- rules/history-tags-releases.md 3.0 KB
- rules/history-worktree.md 3.2 KB
- rules/pr-ci-checks.md 2.9 KB
- rules/pr-description-template.md 3.4 KB
- rules/pr-draft-usage.md 3.1 KB
- rules/pr-reviewers.md 3.0 KB
- rules/pr-small-focused.md 2.7 KB
- rules/pr-squash-merge.md 2.9 KB
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.
- 5d ago First seen · 562 lines · 59 tokens per session scan A ea37c193838d
git-workflow is a skill published in the GitHub repository AsyrafHussin/agent-skills (72 stars, last pushed 8d ago), licensed MIT. It adds 59 tokens to every session and 3,143 once invoked, about $0.0003 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-30.
Other skills, from other repositories
truecourse-hooks
Install, configure, or remove the TrueCourse pre-commit hook.
ring:generating-pr-descriptions
Generating pull request descriptions from git branch changes with automatic title generation, change-type detection, and smart analysis. Uses branch-only scope to avoid full history analysis. Use when preparing a PR for review. Skip when the PR is a single trivial commit or description already exists.
git-commit-integrity
Ensures every commit in a series is what it claims to be — a working, gate-passing snapshot in isolation, not just a slice of a working directory that happened to pass while other changes sat nearby. Covers verifying commit history after the fact, designing pre-commit hooks that check the commit rather than the…
codex-merge-pr
Squash merge a pull request. The commit message comes from this workflow rather than from GitHub, whose own version concatenates every commit on the branch into text no linter ever reads. A briefing script prints the published description, every commit the squash collapses, and the diffstat, then leaves a…
commit
Group changes into one atomic commit, draft a Conventional Commit message in COMMITAGENTMSG, put it through an independent review and the commit-msg gates, confirm it with the operator, then commit and rebase. Use this skill whenever the user asks to commit work in a tbhb repo ("commit this," "commit the staged…
merge-pr
Squash merge a pull request. The commit message comes from this workflow rather than from GitHub, whose own version concatenates every commit on the branch into text no linter ever reads. A briefing script prints the published description, every commit the squash collapses, and the diffstat, then leaves a…