Borrowing it
Nothing to install: this file belongs to r3bl-org/r3bl-open-core. 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/r3bl-org/r3bl-open-core/main/.agents/skills/create-commit-message/SKILL.mdgit clone --depth 1 https://github.com/r3bl-org/r3bl-open-coreWrote 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/skills/r3bl-org/r3bl-open-core/create-commit-message)<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/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/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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 56 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00037 | $0.00722 |
| Opus 5.5 | $0.00015 | $0.00289 |
| Sonnet 5.5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
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 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 — 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 loghistory 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
- Task Tracking (
Task:):- When a commit implements work from a
task/*.mdfile, add aTask:trailer. - Do NOT include any directory prefixes (like
task/ortask/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
- When a commit implements work from a
- Issue/PR Closing (
Closes):- If the commit fully resolves a GitHub Issue or PR, include
Closes #XXX.
- If the commit fully resolves a GitHub Issue or PR, include
- 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]>.
- If you are integrating work from another contributor (e.g., merging a community PR manually), include their attribution:
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]>
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 · 57 lines · 37 tokens per session scan A 8d1d7d2ee6f2
create-commit-message is a skill published in the GitHub repository r3bl-org/r3bl-open-core (486 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 722 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-08-30.
Other skills, from other repositories
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.