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 skills add JayRHa/AgentSkills --skill git-workflowgit clone --depth 1 https://github.com/JayRHa/AgentSkillsWrote 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/jayrha/agentskills/git-workflow)<a href="https://agentmods.dev/skills/jayrha/agentskills/git-workflow"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/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/skills/jayrha/agentskills/git-workflow"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/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.00132 | $0.02089 |
| Opus 5.5 | $0.00053 | $0.00836 |
| Sonnet 5.5 | $0.00026 | $0.00418 |
| Haiku 4.5 | $0.00013 | $0.00209 |
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Overview
This skill provides a disciplined, safe workflow for everyday Git: branching, crafting clean atomic commits, rewriting history with interactive rebase, resolving conflicts, and recovering from mistakes using the reflog. The guiding principle is safety first — never destroy work you cannot recover, always know your escape hatch before running a history-rewriting command.
Keywords: git, branch, commit, rebase, interactive rebase, squash, fixup, reword, cherry-pick, merge, conflict, conflict resolution, reflog, recover lost commits, undo, reset, revert, detached HEAD, force-push, stash, clean history, conventional commits, PR prep.
Golden rules
- Never rewrite history that others have already pulled (shared branches like
main/develop). Rewrite only your own unmerged feature branches. - Before any
rebase,reset --hard, or force-push, note the current commit:git rev-parse HEADor just trust the reflog — it remembers. - Prefer
git push --force-with-leaseover--force. It refuses to clobber commits you haven't seen. - Commit early, commit often locally; clean up into atomic commits before sharing.
- If something looks lost, it almost certainly isn't — go to
git reflog(see references/reflog-recovery.md).
Workflow
1. Orient before acting
Always understand current state first:
git status # working tree + branch
git log --oneline -10 # recent history
git branch -vv # branches + tracking
2. Branch
- Update the base first:
git switch main && git pull --ff-only. - Create the branch:
git switch -c feat/short-description. - Naming:
<type>/<slug>e.g.feat/oauth-login,fix/null-deref,chore/bump-deps,docs/readme. See references/branch-naming.md.
3. Make atomic commits
- One logical change per commit. Stage selectively:
git add -pto split a working tree into focused hunks. - Write a Conventional Commit message (see references/conventional-commits.md):
feat(auth): add OAuth2 PKCE login flow Body explaining WHY, wrapped at ~72 cols. Reference issues. - Verify before committing: re-read
git diff --staged.
What ships with it
8 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.
- examples/squash-feature-branch.md 3.3 KB
- references/branch-naming.md 2.0 KB
- references/conflict-resolution.md 3.5 KB
- references/conventional-commits.md 2.2 KB
- references/interactive-rebase.md 4.2 KB
- references/reflog-recovery.md 3.6 KB
- scripts/git-recover.sh 2.5 KB runs code
- scripts/rebase-safety-check.sh 3.9 KB runs code
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 · 153 lines · 132 tokens per session scan A 9546310741f6
git-workflow is a skill published in the GitHub repository JayRHa/AgentSkills (12 stars, last pushed 2mo ago), licensed MIT. It adds 132 tokens to every session and 2,089 once invoked, about $0.0005 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 skills, from other repositories
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.
commit-message
Generate a clean, conventional commit message from a description of your changes.
developer-workflow
Use when the user is writing, reviewing, debugging, testing, or refactoring code, or wants help with commits and pull requests. Emphasizes reading existing code first, verifying changes, and never inventing APIs.
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
git
Source-control safety for Git. Two rules apply whether or not you read the body. First, never commit, amend, push, tag, rebase, cherry-pick, revert, or reset --hard unless the user asked for that exact write in this session. An explicit request to create a new commit counts anywhere in the user's own task text, but it…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.