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 itsnex1s/awesome-claude-skills --skill git-workflowgit clone --depth 1 https://github.com/itsnex1s/awesome-claude-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/itsnex1s/awesome-claude-skills/git-workflow)<a href="https://agentmods.dev/skills/itsnex1s/awesome-claude-skills/git-workflow"><img src="https://agentmods.dev/badge/skills/itsnex1s/awesome-claude-skills/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/itsnex1s/awesome-claude-skills/git-workflow"><img src="https://agentmods.dev/badge/skills/itsnex1s/awesome-claude-skills/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.00032 | $0.01487 |
| Opus 5.5 | $0.00013 | $0.00595 |
| Sonnet 5.5 | $0.00006 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00149 |
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 2mo 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-workflow
Git workflows, conventional commits, branching strategies, and pull request management.
Conventional Commits
Format: <type>(<scope>): <description>
Types
feat: New feature
fix: Bug fix
docs: Documentation only
style: Formatting, no code change
refactor: Code change, no feature/fix
perf: Performance improvement
test: Adding tests
chore: Build, config, dependencies
ci: CI/CD changes
revert: Revert previous commit
Examples
git commit -m "feat(auth): add OAuth2 login"
git commit -m "fix(api): handle null response"
git commit -m "docs: update README installation"
git commit -m "chore(deps): upgrade React to 19"
git commit -m "refactor(utils): simplify date formatting"
Breaking Changes
git commit -m "feat(api)!: change response format"
# or
git commit -m "feat(api): change response format
BREAKING CHANGE: Response now returns array instead of object"
Branch Naming
Format
<type>/<ticket>-<description>
Examples
git checkout -b feat/AUTH-123-oauth-login
git checkout -b fix/BUG-456-null-pointer
git checkout -b chore/upgrade-dependencies
git checkout -b hotfix/security-patch
Types
feat/ Feature branch
fix/ Bug fix branch
hotfix/ Urgent production fix
chore/ Maintenance
docs/ Documentation
refactor/ Code refactoring
test/ Test additions
Common Workflows
Start New Feature
git checkout main
git pull origin main
git checkout -b feat/TICKET-123-feature-name
Commit Changes
git add -A
git commit -m "feat(scope): description"
Push and Create PR
git push -u origin HEAD
gh pr create --title "feat(scope): description" --body "## Summary\n- Change 1\n- Change 2"
Update Branch with Main
# Rebase (clean history)
git fetch origin
git rebase origin/main
# Or merge (preserves history)
git merge origin/main
Interactive Rebase (squash commits)
git rebase -i HEAD~3 # Last 3 commits
# Change 'pick' to 'squash' or 's' for commits to combine
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.
- 2mo ago First seen · 250 lines · 32 tokens per session scan A df8fac937596
git-workflow is a skill published in the GitHub repository itsnex1s/awesome-claude-skills (5 stars, last pushed 8mo ago), licensed MIT. It adds 32 tokens to every session and 1,487 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-31.
git-workflow compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| git-workflowitsnex1s/awesome-claude-skills | Skill | 5 | 8mo ago | MIT | A | 32 | Claude Code |
| rea-changelog-updatemorluto/rea | Skill | 443k | today | MIT | A | 33 | Claude Code |
| repo-hygieneQwenLM/qwen-code | Skill | 29k | today | Apache-2.0 | A | 48 | Claude Code, Codex |
| gh-skillcli/cli | Skill | 47k | 2d ago | MIT | A | 41 | Claude Code, Codex |
| cw-gatesHmbown/Codewhale | Skill | 41k | 1mo ago | MIT | A | 48 | Claude Code, Codex |
| fanouthashgraph-online/awesome-codex-plugins | Skill | 1.5k | yesterday | Apache-2.0 | A | 68 | Claude Code, Codex |
| atmos-hookscloudposse/atmos | Skill | 1.4k | yesterday | Apache-2.0 | A | 46 | Claude Code |