Borrowing it
Nothing to install: this file belongs to bayesimpact/bayes-platform. 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/bayesimpact/bayes-platform/main/.claude/skills/commit-name/SKILL.mdgit clone --depth 1 https://github.com/bayesimpact/bayes-platformWrote 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/bayesimpact/bayes-platform/commit-name)<a href="https://agentmods.dev/skills/bayesimpact/bayes-platform/commit-name"><img src="https://agentmods.dev/badge/skills/bayesimpact/bayes-platform/commit-name/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/bayesimpact/bayes-platform/commit-name"><img src="https://agentmods.dev/badge/skills/bayesimpact/bayes-platform/commit-name.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.00031 | $0.00640 |
| Opus 5 | $0.00015 | $0.00320 |
| Sonnet 5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
commit-name 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 2d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propose a commit message for the current changes following the Conventional Commits specification. Do NOT stage, commit, or modify any files — only output the suggested message.
Conventional Commits Format
<type>(<scope>): <short summary>
Types
| Type | When to use |
|---|---|
feat |
A new feature or capability |
fix |
A bug fix |
refactor |
Code change that neither fixes a bug nor adds a feature |
chore |
Maintenance tasks, dependency updates, config changes |
ci |
CI/CD pipeline, GitHub Actions, Makefile changes |
docs |
Documentation only |
test |
Adding or updating tests |
perf |
Performance improvement |
style |
Formatting, whitespace, linting (no logic change) |
core |
Cross-cutting changes (changelog, versioning) |
Scope
Optional but encouraged. Use the domain or area affected:
- Domain module name:
AgentSession,Organization,Project,User - Layer:
api,web,ui,api-contracts - Infra/tooling:
security,docker,deps
Use PascalCase for domain entities, lowercase for layers/infra. If the change spans many areas, omit the scope.
Summary rules
- Lowercase first letter, no period at the end
- Imperative mood ("add", "fix", "remove", not "added", "fixes", "removed")
- Under 72 characters total for the first line
- Focus on why/what, not how
Steps
-
Run
git status(never use-uall) andgit diffin parallel to see the changes. If everything is already staged, usegit diff --staged; if both staged and unstaged exist, look at both. -
Analyze the diff and determine the type, optional scope, and a concise summary in imperative mood.
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.
- 2d ago First seen · 67 lines · 31 tokens per session scan A 78cd8323c502
commit-name is a skill published in the GitHub repository bayesimpact/bayes-platform (18 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 640 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-09-14.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.