Borrowing it
Nothing to install: this file belongs to atman-33/kiro-for-codex-ide. 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/atman-33/kiro-for-codex-ide/main/.codex/prompts/generate-commit-message-draft.mdgit clone --depth 1 https://github.com/atman-33/kiro-for-codex-ideWrote 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/atman-33/kiro-for-codex-ide/generate-commit-message-draft)<a href="https://agentmods.dev/commands/atman-33/kiro-for-codex-ide/generate-commit-message-draft"><img src="https://agentmods.dev/badge/commands/atman-33/kiro-for-codex-ide/generate-commit-message-draft/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/atman-33/kiro-for-codex-ide/generate-commit-message-draft"><img src="https://agentmods.dev/badge/commands/atman-33/kiro-for-codex-ide/generate-commit-message-draft.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.00977 |
| Opus 5.5 | $0.00000 | $0.00391 |
| Sonnet 5.5 | $0.00000 | $0.00195 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
generate-commit-message-draft 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Commit Message
You are a coding assistant operating at the root of a Git repository.
Follow the steps below carefully. If any step fails, continue the process and note the reason in the Notes section at the end of the output.
Goal
- Analyze the currently staged changes and generate a commit message.
- Reference the last 5 commit messages to infer the repository’s preferred writing style (format, tone, and conventions).
- Output the final message to
.tmp/commit-message-draft.md, completely overwriting any existing content.
Steps
-
Preconditions
- Assume the working directory is the repository root.
- If any Git command fails, continue and record the cause under
Notes.
-
Check staged files
-
Run:
git diff --staged --name-statusgit diff --staged
-
If there are no staged changes, write the following to
.tmp/commit-message-draft.mdand stop:# Commit Message (Draft) No staged changes were found. -
If staged files exist, proceed.
-
-
Analyze the last 5 commit messages
-
Run:
git log -n 5 --pretty=format:%H%n%s%n%b%n---END--- -
From these messages, infer:
- Title format (e.g.,
feat: ...,Fix ..., etc.) - Language (English or Japanese dominant)
- Title length range (e.g., 50–72 chars)
- Body structure (paragraphs vs. bullet points, use of
BREAKING CHANGE:orRefs #123) - Presence of footers (
Co-authored-by, etc.)
- Title format (e.g.,
-
Adopt a consistent style for the new message.
-
-
Summarize staged changes
- For each file, describe its intent in 1–2 sentences (why, what, how).
- Order the summary by importance: major → minor changes.
- If any destructive or API-breaking modifications are detected, add
BREAKING CHANGE:at the end of the body. - If related issue/PR numbers can be inferred, include
Refs #<number>in the footer.
-
Compose the commit message
- Title:
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 · 121 lines · 0 tokens per session scan A b8fba1aaa37a
generate-commit-message-draft is a command published in the GitHub repository atman-33/kiro-for-codex-ide (16 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 977 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
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).
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
constitution
Add, update, or remove engineering principles in docs/project/engineering-principles.md with atomic versioned commits.
commit
Stage and commit with a conventional-commit message the auto-release bot can read.
branch-commit
Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…
approve-proposed
Atomically persist every file marked PROPOSED in the most recent prior assistant turn's ### Artifact changes block, promoting staged content to real files. Invoked on request only. Use when that block contained files marked PROPOSED and you have accepted the inline content of each. Do not use when the prior turn had…