Borrowing it
Nothing to install: this file belongs to jayminwest/kotadb. 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/jayminwest/kotadb/develop/.claude/commands/git/commit.mdgit clone --depth 1 https://github.com/jayminwest/kotadbWrote 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/jayminwest/kotadb/commit)<a href="https://agentmods.dev/commands/jayminwest/kotadb/commit"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/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/jayminwest/kotadb/commit"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/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.01114 |
| Opus 5.5 | $0.00000 | $0.00446 |
| Sonnet 5.5 | $0.00000 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00111 |
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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/commit
Template Category: Message-Only
Generate a git commit message for the staged work.
Variables
- agent_name: $1 (planner or implementor)
- issue_type: $2 (feature, bug, chore)
- issue_json: $3 (GitHub issue payload)
Instructions
- Commit message format:
<issue_type>: ${issue_number} - <short description>. - Description must be ≤ 60 characters, present tense, no trailing period.
- Preface the body (if needed) with
Generated with ADW ID: <adw_id>is handled elsewhere—only craft the subject. - Review
git diff HEADto understand staged changes before generating the message. - DO NOT execute git commands (staging/committing is handled by the orchestration layer).
CRITICAL: Commit Message Validation Rules
Your commit message will be validated by automation/adws/adw_modules/validation.py. It MUST pass these checks:
Format Requirements
- Conventional Commits format:
<type>(<scope>): <subject> - Valid types: feat, fix, chore, docs, test, refactor, perf, ci, build, style
- Subject length: 1-72 characters (keep under 60 for best practices)
- Optional scope: You can add a scope in parentheses after the type (e.g.,
feat(api):)
Meta-Commentary Patterns (FORBIDDEN in first line)
DO NOT include these phrases anywhere in the commit message subject line:
- ❌
based on - ❌
the commit should - ❌
here is - ❌
this commit - ❌
i can see - ❌
looking at - ❌
the changes - ❌
let me
These patterns indicate agent reasoning leakage. The commit message should be a direct statement, not a description of your thought process.
Examples
✅ CORRECT (these will pass validation):
chore: 98 - document test path resolution strategy
feat: 123 - add rate limiting middleware
fix: 456 - resolve API key validation bug
docs: 789 - update authentication guide
❌ INCORRECT (these will FAIL validation):
Based on the changes, I can see this is a documentation update
The commit should be: chore - update docs
Here is the commit message for the changes
This commit documents the test path resolution strategy
Looking at the diff, the changes add rate limiting
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 · 129 lines · 0 tokens per session scan A 928b003166c1
commit is a command published in the GitHub repository jayminwest/kotadb (100 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,114 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-30.
Other commands, from other repositories
commit
When you receive this command, do the following.
pre-commit-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de créer un commit, pour garantir que le code respecte les standards du projet.
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).
fest-commit
Commit changes with festival traceability metadata.
pre-commit-audit
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers. Use when the user requests a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode…
merge
You are executing the /hydra:merge command. Merge a worktree branch back into the current branch.