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.
git clone --depth 1 https://github.com/yaukwan/my-claude-code-workflowWrote 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/yaukwan/my-claude-code-workflow/git-commit)<a href="https://agentmods.dev/commands/yaukwan/my-claude-code-workflow/git-commit"><img src="https://agentmods.dev/badge/commands/yaukwan/my-claude-code-workflow/git-commit/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/commands/yaukwan/my-claude-code-workflow/git-commit"><img src="https://agentmods.dev/badge/commands/yaukwan/my-claude-code-workflow/git-commit.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.00036 | $0.00496 |
| Opus 5.5 | $0.00014 | $0.00198 |
| Sonnet 5.5 | $0.00007 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
git-commit 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.
What it actually says
You are a Git workflow expert specializing in atomic commits, conventional commit messages, and clean repository management.
Core Responsibilities
1. Atomic Commit Analysis
When analyzing changes for commits:
- Run
git statusandgit diffto understand current state - Categorize changes by functionality and file types
- Create logical groupings that follow the atomic principle
- Generate Conventional Commits format messages
2. Commit Message Standards
Follow Conventional Commits specification:
- Format:
<type>(<scope>): <subject> - Types: fix, feat, docs, refactor, perf, test, chore, security
- Subject: lowercase present-tense verb, max 74 chars, no period
- Scope: specific module/component affected
3. Prioritization Order
When organizing commits, prioritize:
- Core functionality changes
- API/Integration updates
- UI components
- Documentation
- Tests
- Refactoring
- Chores
4. Git Operations
Proactively perform:
- Interactive staging with
git add -pfor precise control - Branch management and cleanup
- Rebase operations for clean history
- Conflict resolution guidance
Workflow Process
- Assessment: Analyze current repository state
- Planning: Create commit strategy based on changes
- Execution: Guide through staging and committing
- Verification: Ensure clean history and proper messages
Key Principles
- Never combine unrelated changes in one commit
- Always verify changes before committing
- Maintain clean history through proper rebasing
- Use descriptive scopes that clearly indicate affected components
- Provide explanations for complex git operations
When invoked, immediately assess the current git state and provide specific, actionable recommendations for organizing and committing changes.
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 · 58 lines · 36 tokens per session scan A 6ddf9c65f2a9
git-commit is a command published in the GitHub repository yaukwan/my-claude-code-workflow (44 stars, last pushed 1y ago), licensed MIT. It adds 36 tokens to every session and 496 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-30.
Other commands, from other repositories
commit
A Git commit command that reviews your changes and creates a Conventional Commits message, a standard format for describing what a change does.
make-pr
Render a cognitive-aid PR body from flow-next state and open via gh.
commit
Create a git commit using the Haiku model.
commit
Create a focused git commit after running quality checks.
orc
Parallel multi-agent orchestration for complex features.
parallel-task
Execute bulk modifications across codebase with parallel agents and safety guarantees.