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/hoangatg/ai-agent-toolkit/git-workflownpx skills add hoangatg/ai-agent-toolkit --skill git-workflowgit clone --depth 1 https://github.com/hoangatg/ai-agent-toolkitWrote 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/hoangatg/ai-agent-toolkit/git-workflow)<a href="https://agentmods.dev/skills/hoangatg/ai-agent-toolkit/git-workflow"><img src="https://agentmods.dev/badge/skills/hoangatg/ai-agent-toolkit/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.00029 | $0.00817 |
| Opus 5 | $0.00015 | $0.00409 |
| Sonnet 5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00082 |
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 today.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Good git habits make teams fast. Bad ones make teams suffer.
1. Branching Strategies
| Strategy | Best For | Complexity |
|---|---|---|
| GitHub Flow | Small teams, continuous deploy | Low |
| GitFlow | Release cycles, versioned software | Medium |
| Trunk-Based | CI/CD, feature flags | Low-Medium |
GitHub Flow (Recommended for most)
main (always deployable)
└── feature/xyz → PR → Review → Merge → Deploy
Branch Naming
| Type | Pattern | Example |
|---|---|---|
| Feature | feature/short-desc |
feature/user-auth |
| Bugfix | fix/short-desc |
fix/login-crash |
| Hotfix | hotfix/short-desc |
hotfix/payment-error |
| Chore | chore/short-desc |
chore/update-deps |
2. Conventional Commits
Format
<type>(<scope>): <description>
[optional body]
[optional footer]
Types
| Type | When |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Formatting, no logic change |
refactor |
Code restructuring |
perf |
Performance improvement |
test |
Adding/fixing tests |
chore |
Build, CI, tooling |
revert |
Reverting a commit |
Breaking Changes
feat(api)!: change response format
BREAKING CHANGE: response.data is now an array
3. Pull Request Best Practices
| Principle | Application |
|---|---|
| Small PRs | < 400 lines changed |
| Clear title | Conventional commit format |
| Description | What, why, how, testing done |
| Screenshots | For UI changes |
| Self-review first | Review your own diff before submitting |
PR Template
## What
Brief description of changes
## Why
Context and motivation
## Testing
How this was tested
## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No breaking changes
4. Code Review
| Speed | Principle |
|---|---|
| < 24h | Review within one business day |
| Approve or comment | Don't leave PRs hanging |
| Constructive | Suggest alternatives, not just criticize |
| Distinguish | Blockers vs. nitpicks vs. questions |
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.
- today First seen · 140 lines · 29 tokens per session scan A 45d258d423be
git-workflow is a skill published in the GitHub repository hoangatg/ai-agent-toolkit (1 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 817 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.
opencode
Delegate coding tasks to the OpenCode CLI for feature work, refactoring, PR review, and autonomous-style runs. Requires opencode installed where the agent can execute shell commands.
codex
Delegate coding tasks to the OpenAI Codex CLI for features, refactoring, PR reviews, and batch fixes. Requires the codex CLI and typically a git repository.
deepnote
DeepNote knowledge base: persistent interlinked markdown wiki with ingest, query, lint, link graph and history.