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 justanesta/claude-code-resources --skill git-workflow-patternsgit clone --depth 1 https://github.com/justanesta/claude-code-resourcesWrote 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/justanesta/claude-code-resources/git-workflow-patterns)<a href="https://agentmods.dev/skills/justanesta/claude-code-resources/git-workflow-patterns"><img src="https://agentmods.dev/badge/skills/justanesta/claude-code-resources/git-workflow-patterns/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/justanesta/claude-code-resources/git-workflow-patterns"><img src="https://agentmods.dev/badge/skills/justanesta/claude-code-resources/git-workflow-patterns.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.00062 | $0.01989 |
| Opus 5.5 | $0.00025 | $0.00796 |
| Sonnet 5.5 | $0.00012 | $0.00398 |
| Haiku 4.5 | $0.00006 | $0.00199 |
Grade A, and why
git-workflow-patterns 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Patterns
Practical git workflow patterns for teams emphasizing clean history, safe collaboration, and reliable releases.
Core Principles
- Atomic commits - Each commit represents one logical change that compiles and passes tests
- Clear history - Commit messages explain why, not what; diffs explain what
- Branch hygiene - Short-lived feature branches, deleted after merge
- Linear history where possible - Rebase feature branches before merging to main
- Automate the boring parts - CI checks, changelog generation, version bumps
Branching Strategies
Use trunk-based development for most teams
# Create a short-lived feature branch from main
git checkout main
git pull origin main
git checkout -b feat/add-user-auth
# Work on the feature (keep branch lifetime under 2 days)
git add src/auth.py src/middleware.py
git commit -m "feat(auth): add JWT-based user authentication"
# Update from main before pushing
git fetch origin main
git rebase origin/main
git push -u origin feat/add-user-auth
Key strategy comparison:
- Trunk-based: Everyone commits to main (or short branches). Best for CI/CD and small teams.
- GitHub Flow: Feature branches + pull requests into main. Best for open source and mid-size teams.
- GitFlow: develop/release/hotfix branches. Best for scheduled releases with strict versioning.
See branching-strategies.md for:
- Detailed trunk-based development workflow
- GitHub Flow step-by-step
- GitFlow branch naming and lifecycle
- Release branch management
Commit Message Conventions
Follow Conventional Commits format
# Format: <type>(<scope>): <description>
#
# Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore
# Breaking changes: add ! after type or BREAKING CHANGE in footer
git commit -m "feat(api): add pagination to /users endpoint"
git commit -m "fix(auth): prevent token refresh race condition"
git commit -m "docs(readme): update installation instructions"
# Breaking change
git commit -m "feat(api)!: change response format to JSON:API spec
BREAKING CHANGE: All API responses now follow JSON:API format.
Clients must update their parsers accordingly."
What ships with it
5 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.
- 2mo ago First seen · 254 lines · 62 tokens per session scan A fdd60afbe9d3
git-workflow-patterns is a skill published in the GitHub repository justanesta/claude-code-resources (2 stars, last pushed 6mo ago), licensed MIT. It adds 62 tokens to every session and 1,989 once invoked, about $0.0002 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
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
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-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.