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 halflength-ampleness75/claude-code-recipes --skill git-workflowgit clone --depth 1 https://github.com/halflength-ampleness75/claude-code-recipesWrote 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/halflength-ampleness75/claude-code-recipes/git-workflow)<a href="https://agentmods.dev/skills/halflength-ampleness75/claude-code-recipes/git-workflow"><img src="https://agentmods.dev/badge/skills/halflength-ampleness75/claude-code-recipes/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/halflength-ampleness75/claude-code-recipes/git-workflow"><img src="https://agentmods.dev/badge/skills/halflength-ampleness75/claude-code-recipes/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.00000 | $0.01533 |
| Opus 5.5 | $0.00000 | $0.00613 |
| Sonnet 5.5 | $0.00000 | $0.00307 |
| Haiku 4.5 | $0.00000 | $0.00153 |
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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow
Git conventions: branch naming, conventional commits, PR format, squash strategy, and protected branches.
Branch Naming
Use the format: <type>/<ticket>-<short-description>
| Type | Purpose | Example |
|---|---|---|
feat/ |
New feature | feat/PROJ-123-user-avatars |
fix/ |
Bug fix | fix/PROJ-456-login-redirect |
chore/ |
Maintenance, deps, config | chore/upgrade-react-19 |
docs/ |
Documentation only | docs/api-authentication-guide |
refactor/ |
Code restructuring | refactor/extract-auth-module |
test/ |
Adding or fixing tests | test/order-service-coverage |
hotfix/ |
Urgent production fix | hotfix/payment-timeout |
Rules
- Always branch from
main(ordevelopif using Git Flow) - Use lowercase and hyphens — no underscores, no camelCase
- Include the ticket number when a tracker exists
- Keep descriptions under 5 words
- Delete branches after merging
Conventional Commits
Follow the Conventional Commits specification.
Format
<type>(<scope>): <subject>
<body>
<footer>
Types
| Type | When to Use |
|---|---|
feat |
New feature visible to users |
fix |
Bug fix |
docs |
Documentation changes only |
style |
Formatting, whitespace (no logic changes) |
refactor |
Code change that neither fixes a bug nor adds a feature |
perf |
Performance improvement |
test |
Adding or updating tests |
build |
Build system or dependencies |
ci |
CI/CD pipeline changes |
chore |
Other changes that don't modify src or test files |
revert |
Reverts a previous commit |
Rules
- Subject line under 72 characters
- Use imperative mood — "add feature" not "added feature" or "adds feature"
- No period at the end of the subject
- Scope is optional but encouraged — use the module or component name
- Body explains why, not what — the diff shows what changed
- Footer for breaking changes and issue references
What ships with it
1 file 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.
- 1mo ago First seen · 207 lines · 0 tokens per session scan A 07eda98311a6
git-workflow is a skill published in the GitHub repository halflength-ampleness75/claude-code-recipes (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,533 tokens. 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
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
git-workflow
Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
atomic-git-discipline
Compressed commit message and PR body generator. Cuts noise from both while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious; PR bodies state only what the diff can't show, 120 words max. Use when user says "write a commit", "commit message", "generate…