Borrowing it
Nothing to install: this file belongs to watt-mind/coach. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/watt-mind/coach/master/.claude/commands/commit.mdgit clone --depth 1 https://github.com/watt-mind/coachWrote 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/watt-mind/coach/commit)<a href="https://agentmods.dev/commands/watt-mind/coach/commit"><img src="https://agentmods.dev/badge/commands/watt-mind/coach/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/watt-mind/coach/commit"><img src="https://agentmods.dev/badge/commands/watt-mind/coach/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.00000 | $0.02302 |
| Opus 5.5 | $0.00000 | $0.00921 |
| Sonnet 5.5 | $0.00000 | $0.00460 |
| Haiku 4.5 | $0.00000 | $0.00230 |
Grade A, and why
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 2mo 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Management Instructions
Your core responsibility is to systematically create logical, clean commits from large-scale code changes. You must adhere to the following principles and workflows:
Core Principles
- Logical Grouping: Group related files that share common functionality or purpose
- Manual Commit Messages: Write clear, descriptive one-line commit messages following conventional commit format
- Strategic Progression: Follow logical implementation order (core → infrastructure → endpoints → frontend)
- Clean History: Maintain readable git history with focused, single-purpose commits
- Systematic Approach: Process all changes methodically without skipping files
- Efficiency: Commit multiple related files together (not limited to 1-2) for faster processing
CRITICAL: Commit Workflow Pattern
⚠️ ALWAYS FOLLOW THIS EXACT SEQUENCE ⚠️
✅ Standard Commit Pattern (ALWAYS USE THIS)
# 1. Run linter to ensure code standards
pnpm run lint
# 2. Stage related files (multiple files OK if logically related)
git add components/ComponentA.vue components/ComponentB.vue components/ComponentC.vue
# 3. Create commit with one-line message (lowercase subject)
git commit -m "refactor(components): update component error handling and data flow"
# 4. Verify commit was created
git log --oneline -1
File Grouping Strategies
- Related Endpoints: Group endpoints from the same domain (assets, integrations, billing)
- Functional Areas: Group by business logic (auth, admin, user management)
- Infrastructure: Group core utilities, middleware, and configuration files
- Frontend Components: Group related Vue components and composables
- Pages: Group page files by functional area
- Multiple Files OK: You can commit many files together if they're part of the same logical change
Logical Progression Order
- Core Infrastructure (auth middleware, utilities, types)
- Server API (API endpoints and services)
- Composables (Vue composables and utilities)
- Pages (Nuxt page components)
- Components (Vue components)
- Configuration (package.json, configs, scripts)
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.
- 2mo ago First seen · 299 lines · 0 tokens per session scan A b3c5d8c03f71
commit is a command published in the GitHub repository watt-mind/coach (105 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,302 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.
commit compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| commitwatt-mind/coach | Command | 105 | 14d ago | Apache-2.0 | A | 0 | Claude Code |
| quick-pushjmagar/claude-homelab | Command | 87 | 1mo ago | MIT | A | 15 | Claude Code |
| commit-push-prpablo-albaladejo/kaiord | Command | 11 | 4d ago | MIT | A | 14 | Claude Code |
| commitpablo-albaladejo/kaiord | Command | 11 | 4d ago | MIT | A | 4 | Claude Code |
| standupvvedantb/eva | Command | 101 | yesterday | MIT | A | 0 | Claude Code |
| gitazrtydxb/procoder | Command | 211 | 11d ago | Apache-2.0 | A | 20 | Claude Code |
| session-reportdamusix/atomic-claude | Command | 115 | 4d ago | MIT | A | 31 | Claude Code |