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 commands/swesmith/davila7__claude-code-templates.734b8a50/git-workflowgit clone --depth 1 https://github.com/swesmith/davila7__claude-code-templates.734b8a50Wrote 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/commands/swesmith/davila7__claude-code-templates.734b8a50/git-workflow)<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/git-workflow"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/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.1 | $0.00000 | $0.01264 |
| Opus 5 | $0.00000 | $0.00632 |
| Sonnet 5 | $0.00000 | $0.00253 |
| Haiku 4.5 | $0.00000 | $0.00126 |
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.
This is a copy
100% identical to git-workflow — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Helper
Manage Git workflows with best practices and common operations.
Purpose
This command helps you perform common Git operations following best practices for collaborative development.
Usage
/git-workflow
What this command does
- Guides through Git operations with proper workflow
- Suggests best practices for commits and branches
- Helps with conflict resolution and merging
- Provides templates for commit messages
- Manages branching strategies (Git Flow, GitHub Flow)
Common Workflows
Feature Development
# Create and switch to feature branch
git checkout -b feature/user-authentication
# Work on your feature
# ... make changes ...
# Stage and commit changes
git add .
git commit -m "feat: add user authentication system
- Implement login/logout functionality
- Add password validation
- Create user session management
- Add authentication middleware"
# Push feature branch
git push -u origin feature/user-authentication
# Create pull request (via GitHub/GitLab interface)
Hotfix Workflow
# Create hotfix branch from main
git checkout main
git checkout -b hotfix/security-patch
# Fix the issue
# ... make changes ...
# Commit the fix
git commit -m "fix: resolve security vulnerability in auth module
- Patch XSS vulnerability in login form
- Update input validation
- Add CSRF protection"
# Push and create urgent PR
git push -u origin hotfix/security-patch
Sync with Remote
# Update main branch
git checkout main
git pull origin main
# Update feature branch with latest main
git checkout feature/your-feature
git rebase main
# OR
git merge main
Commit Message Conventions
Conventional Commits Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Common Types
- feat: New feature
- fix: Bug fix
- docs: Documentation changes
- style: Code style changes (formatting, etc.)
- refactor: Code refactoring
- test: Adding or updating tests
- chore: Maintenance tasks
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 · 239 lines · 0 tokens per session scan A c1558e977d2d
git-workflow is a command published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,264 tokens. A static security scan graded it A with 0 findings. It is 100% identical to git-workflow, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.