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/kambleakash0/agent-skills/git-workflownpx skills add kambleakash0/agent-skills --skill git-workflowgit clone --depth 1 https://github.com/kambleakash0/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/kambleakash0/agent-skills/git-workflow)<a href="https://agentmods.dev/skills/kambleakash0/agent-skills/git-workflow"><img src="https://agentmods.dev/badge/skills/kambleakash0/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.00060 | $0.00883 |
| Opus 5 | $0.00030 | $0.00441 |
| Sonnet 5 | $0.00012 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00088 |
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Skill
You are a Git workflow expert. Guide the user through best-practice Git operations step by step.
Detect context
Before doing anything, run:
git status
git log --oneline -10
Use the output to understand:
- Current branch
- Uncommitted changes
- Recent commit history
Then ask the user what they want to do if it is not already clear from their message.
Branching
When creating a new branch:
- Confirm the base branch (usually
mainordevelop). - Pull the latest changes:
git pull origin <base>. - Create a descriptive branch name following the pattern
<type>/<short-description>:feat/add-login-pagefix/null-pointer-in-authchore/update-dependenciesdocs/api-reference
- Create and switch:
git checkout -b <branch-name>.
Committing
Write commits that follow the Conventional Commits spec:
<type>(<optional scope>): <short imperative summary>
[optional body explaining *why*, not what]
[optional footer: BREAKING CHANGE, closes #issue]
Allowed types: feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert.
Rules:
- Summary is ≤ 50 characters, lowercase, no trailing period.
- Use the body for non-obvious reasoning.
- Reference issues with
closes #<n>orrefs #<n>.
When the user has staged changes, suggest a commit message based on the diff:
git diff --cached
Pull Requests
Before opening a PR:
-
Rebase onto the latest base branch to keep history linear:
git fetch origin git rebase origin/main -
Run tests and linters.
-
Push the branch:
git push -u origin <branch-name>. -
Draft a PR description using this template:
## What & Why
<!-- One paragraph explaining the change and its motivation. -->
## How
<!-- Key implementation decisions. -->
## Testing
<!-- How was this tested? -->
## Checklist
- [ ] Tests pass
- [ ] Docs updated (if needed)
- [ ] No unintended side effects
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 · 137 lines · 60 tokens per session scan A adddc1047102
git-workflow is a skill published in the GitHub repository kambleakash0/agent-skills (8 stars, last pushed 18d ago), licensed MIT. It adds 60 tokens to every session and 883 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-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
conductor-revert
Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.
ship
Commit and push the current work properly — lint, run the release gate, write a detailed commit message, push to GitHub. Use whenever work reaches a milestone or the user says ship it, commit, or push.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.