Borrowing it
Nothing to install: this file belongs to future-architect/uzomuzo-oss. 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/future-architect/uzomuzo-oss/main/.github/prompts/commit.prompt.mdgit clone --depth 1 https://github.com/future-architect/uzomuzo-ossWrote 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/future-architect/uzomuzo-oss/commit)<a href="https://agentmods.dev/commands/future-architect/uzomuzo-oss/commit"><img src="https://agentmods.dev/badge/commands/future-architect/uzomuzo-oss/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/future-architect/uzomuzo-oss/commit"><img src="https://agentmods.dev/badge/commands/future-architect/uzomuzo-oss/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.00014 | $0.00304 |
| Opus 5.5 | $0.00006 | $0.00122 |
| Sonnet 5.5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
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
Pre-Commit Checks
Before creating a commit, run all of the following checks in order. If any check fails, stop immediately and report.
Step 1: Branch Verification
git branch --show-current
- Confirm you are NOT on
main/master(double-check even though Branch Protection blocks it) - Confirm you are on the intended branch
Step 2: Build
go build ./...
Step 3: Test
go test -race ./...
Step 4: Vet & Lint
go vet ./...
golangci-lint run
Step 5: Staging Review
git status
git diff --cached
git diff
- Ensure no secrets (.env, credentials, API keys) are staged
- Ensure no unintended files are included
Commit
Only after all checks pass:
- Stage relevant files (prefer explicit filenames over
git add -A) - Commit with a conventional commits format message (always in English)
- Run
git statusafter commit to verify success
If the user provides a commit message argument, use it. Otherwise, generate an appropriate message from the 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 · 14 tokens per session scan A 8e8cdee23036
commit is a command published in the GitHub repository future-architect/uzomuzo-oss (42 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 304 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-09-07.
Other commands, from other repositories
fix-tests-execute
Phase 2 of fixing-tests: Fix Execution - investigate, classify, fix, verify, and commit each work item.
verify
Run verification commands and confirm output before making success claims. Use before committing, creating PRs, or claiming work is complete. Evidence before assertions, ALWAYS.
implement-revalidate
Read by /implement when the user asks to re-validate (D-CMD-REF-HAND).
build
Implement the next task incrementally — build, test, verify, commit.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.