Borrowing it
Nothing to install: this file belongs to kavo-labs/kavo. 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/kavo-labs/kavo/main/.claude/commands/commit.mdgit clone --depth 1 https://github.com/kavo-labs/kavoWrote 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/kavo-labs/kavo/commit)<a href="https://agentmods.dev/commands/kavo-labs/kavo/commit"><img src="https://agentmods.dev/badge/commands/kavo-labs/kavo/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/kavo-labs/kavo/commit"><img src="https://agentmods.dev/badge/commands/kavo-labs/kavo/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.00008 | $0.00543 |
| Opus 5.5 | $0.00003 | $0.00217 |
| Sonnet 5.5 | $0.00002 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00054 |
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 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 creating one or more well-scoped git commits from the current working changes.
Context
- Current status: !
git status --short - Current branch: !
git rev-parse --abbrev-ref HEAD - Staged diff stat: !
git diff --cached --stat - Unstaged diff stat: !
git diff --stat - Recent commits (for style): !
git log --oneline -10
Your task
Split every change in the working tree — staged and unstaged — into cohesive logical commits, grouped by intent rather than by folder, until the tree is clean or only intentionally-excluded files remain.
Message format is Conventional Commits; the type vocabulary is in the
conventions skill.
Rules
These are the parts that are specific to this repo, or that differ from what you would otherwise do by default:
- Stage with explicit pathspecs.
git resetto clear the index, thengit add <specific files>per group. Nevergit add -Aorgit add .— they silently sweep in whatever else is in the tree. - Config and tooling go in their own commit, ahead of the code that depends on them, and docs stay separate from implementation unless the two are trivially coupled.
- Do NOT push, and do NOT amend. This command only ever creates new
commits;
/pris what pushes. - No co-author trailers unless this repo's recent commits already use them
— check
git log, do not assume. - Keep nested parentheses out of commit messages. release-please parses
the whole message and a
outer(inner())code span can defeat its parser (fix commit could not be parsed→ the commit is dropped from the changelog). WritemetadataForofrelation.target(), notmetadataFor(relation.target()). - Keep a file whole in its best-fitting commit rather than reaching for patch staging; split a single file across commits only when its changes are genuinely unrelated.
- Finish by printing each commit (hash + subject) and confirming
git statusis clean.
$ARGUMENTS
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 · 52 lines · 8 tokens per session scan A daf2c1d7bd83
commit is a command published in the GitHub repository kavo-labs/kavo (17 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 543 once invoked, about $0.0000 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-09-02.
Other commands, from other repositories
speckit.companion.living-sync
Sync living specs from your current changes — group working-tree changes (uncommitted included) by capability and update every affected spec in one pass (opt-in, update-not-regenerate, never halts).
push-changes
If no topic provided, just document the recent changes. If a topic is provided, focus on documenting that topic.
sync-tutorials
Commit and push your tutorials to the GitHub repository for backup and mobile reading.
git-commit
Based on the above changes, create a single git commit. Use the Angular commit message format：.
commit-push-pr
Commit, push, and open a PR (includes changeset creation).
commit
Based on the above changes, create a single git commit.