create-commit-message

create-commit-message is a skill for Claude Code, Codex from r3bl-org/r3bl-open-core. It costs 37 tokens per session (722 once invoked), scanned A, original, Apache-2.0.

A set of rules for writing Git commit messages, which describe changes saved in a Git repository. It covers subject-line format, length, scope labels, and footer information.

In plain words
What is it for?
Use it when creating a commit message for code changes, especially when the project expects a specific scope prefix or footer format.
Why use it?
It helps keep commit history consistent and readable, while avoiding formatting mistakes in task or pull-request details.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/r3bl-org/r3bl-open-core/create-commit-message
Any agent
npx skills add r3bl-org/r3bl-open-core --skill create-commit-message
Clone the repo
git clone --depth 1 https://github.com/r3bl-org/r3bl-open-core

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for create-commit-message

README.md
[![agentmods](https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/create-commit-message.svg)](https://agentmods.dev/skills/r3bl-org/r3bl-open-core/create-commit-message)
Your own site
<a href="https://agentmods.dev/skills/r3bl-org/r3bl-open-core/create-commit-message"><img src="https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/create-commit-message.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 722 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00722
Opus 5 $0.00018 $0.00361
Sonnet 5 $0.00007 $0.00144
Haiku 4.5 $0.00004 $0.00072

Measured 4d ago against content hash 8d1d7d2ee6f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-commit-message 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 4d 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.

.agents/skills/create-commit-message/SKILL.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Commit Message Skill

You are an expert at writing clean, standard, and highly descriptive git commit messages. When asked to create a commit message, follow these exact guidelines:

1. Scope Prefix (Mandatory)

Start the subject line with a scope prefix in brackets, e.g., [tui], [core], [macro].

  • Always scan the recent git log history for the files you are modifying to determine the appropriate prefix. For example: git log --oneline -- <file_path> will show you what prefix is typically used for that component.

2. Formatting & Length Constraints

  • Subject Line: Keep the subject line (including the scope prefix) to a maximum of 72 characters.
  • Body: Wrap the commit message body to 72 characters per line.
  • Tone: Use the imperative mood in the subject line (e.g., "Add feature" not "Added feature").

3. Trailer Block (Footers)

All trailers MUST be grouped together in a single contiguous block at the absolute end of the commit message.

  • There must be exactly one blank line before the start of the trailer block.
  • There must be zero blank lines between the trailers themselves.

Required / Optional Trailers

  1. Task Tracking (Task:):
    • When a commit implements work from a task/*.md file, add a Task: trailer.
    • Do NOT include any directory prefixes (like task/ or task/done/) in the filenames.
    • For multiple tasks, list them on separate lines with a comma ending each line except the last.
      Task: one.md,
            two.md
      
  2. Issue/PR Closing (Closes):
    • If the commit fully resolves a GitHub Issue or PR, include Closes #XXX.
  3. Attribution (Co-authored-by:):
    • If you are integrating work from another contributor (e.g., merging a community PR manually), include their attribution: Co-authored-by: Name <[email protected]>.

Example

[tui] Add DECCKM tracking and refactor parser state

This commit integrates the DECCKM (Cursor Key Mode) tracking logic from
PR #470, adding the missing `cursor_key_mode` field to the terminal
state and validating it with a new conformance integration test.

Task: prepare-v0.8.0-meta-task.md,
      pty-mux-bracketed-paste.md
Closes #470
Co-authored-by: Cecile Tonglet <[email protected]>

Read the full file on GitHub · 57 lines

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.

  1. 4d ago First seen · 57 lines · 37 tokens per session scan A 8d1d7d2ee6f2

Subscribe to this mod's changes

create-commit-message is a skill published in the GitHub repository r3bl-org/r3bl-open-core (484 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 722 once invoked, about $0.0002 per session on Opus 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-08-30.