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 agents/yaukwan/my-claude-code-workflow/git-commit-expertgit clone --depth 1 https://github.com/yaukwan/my-claude-code-workflowWhat 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.00038 | $0.00528 |
| Opus 5 | $0.00019 | $0.00264 |
| Sonnet 5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
git-commit-expert 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 2d 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
- Context Check: Verify current directory and branch with
pwdandgit branch - Assessment: Analyze current repository state with
git statusandgit diff - 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.
- 2d ago First seen · 59 lines · 38 tokens per session scan A a04ec6a685a6
git-commit-expert is an agent published in the GitHub repository yaukwan/my-claude-code-workflow (44 stars, last pushed 1y ago), licensed MIT. It adds 38 tokens to every session and 528 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
brainstorm-facilitator
Runs the operator's brainstorm phase (phase 2, machine/phases-registry.json) — spawned by Kiln as an agent-team TEAMMATE (its own context, its own mailbox, the operator converses in its window) when agent teams are enabled; when they are not, this seat runs nowhere at all — Kiln facilitates the sketchbook itself…
usage-tracking-specialist
You are an expert in usage-based billing, quota management, and performance-optimized tracking systems. Your mission is to implement AI generation tracking and limit enforcement for id8composer.
integration-verifier
Verifies that the tasks of a completed build actually wire together. Dispatched once at /execute Step 4 for multi-task specs. Read-only -- cannot modify the codebase. Checks cross-task wiring + global acceptance, not per-task acceptance.
cadence-code-reviewer
Reviews an implementer's diff against repo conventions. Second of two review stages. Runs AFTER cadence-spec-reviewer approves. Checks code style, naming, error handling, test design — quality of how the change was made, not whether the right thing was made. Conflicts with spec-reviewer's findings are resolved by spec…
handoff-writer
你是 cadence 工作流的 handoff 写入 subagent。职责：根据主 agent 提取的候选 JSON，执行所有档案写入。.