agentmods.dev

bayes-platform: Skill for Claude Code

.claude/skills/commit-name/SKILL.md

commit-name is a skill for Claude Code from bayesimpact/bayes-platform. It costs 31 tokens per session (640 once invoked), scanned A, original, MIT.

A helper that examines the current code changes and suggests a commit message using the Conventional Commits format. It does not stage files, create a commit, or change the project.

In plain words
What is it for?
Use it to prepare a commit title describing a feature, fix, refactor, test, documentation change, or other update.
Why use it?
It removes the need to write a suitable summary from scratch while keeping the changes untouched.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is bayesimpact/bayes-platform's own configuration. It tells Claude Code how to work on bayes-platform itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bayes-platform configures →

not rated 23repo yesterday A scan 31 tokens original MIT
View source ↗ bayesimpact/bayes-platform bayesimpact.org
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/bayesimpact/bayes-platform/main/.claude/skills/commit-name/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/bayesimpact/bayes-platform

Made for: Claude Code.

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 commit-name

README.md
[![agentmods](https://agentmods.dev/badge/skills/bayesimpact/bayes-platform/commit-name/github.svg)](https://agentmods.dev/skills/bayesimpact/bayes-platform/commit-name)
Your own site
<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.

agentmods 80×15 button for commit-name

Your own site · 80×15
<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>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 640 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00031 $0.00640
Opus 5.5 $0.00012 $0.00256
Sonnet 5.5 $0.00006 $0.00128
Haiku 4.5 $0.00003 $0.00064

Measured 1mo ago against content hash 78cd8323c502, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

.claude/skills/commit-name/SKILL.md · 67 lines

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

  1. Run git status (never use -uall) and git diff in parallel to see the changes. If everything is already staged, use git diff --staged; if both staged and unstaged exist, look at both.

  2. Analyze the diff and determine the type, optional scope, and a concise summary in imperative mood.

Read the full file on GitHub · 67 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. 1mo ago First seen · 67 lines · 31 tokens per session scan A 78cd8323c502

Subscribe to this mod's changes

commit-name is a skill published in the GitHub repository bayesimpact/bayes-platform (23 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 640 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-14.

CommitsGit and workflow
Related

commit-name compared with skills from other repositories

commit-name next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
commit-namebayesimpact/bayes-platformSkill23yesterdayMITA31Claude Code
create-prprisma/ormSkill48kyesterdayApache-2.0A48Claude Code, Codex
git-commitThinkInAIXYZ/deepchatSkill6.4kyesterdayApache-2.0A15Claude Code, Codex
repo-syncdavidondrej/skillsSkill4.3k3d agoMITA25Claude Code, Codex
engineer-bot-opsmakecindy/cindySkill9.3kyesterdayApache-2.0A57Claude Code, Codex
mcore-split-prNVIDIA/skillsSkill3.9kyesterdayApache-2.0A25Claude Code
git-commit-writermergisi/awesome-openclaw-agentsSkill4.1k2d agoMITA53Claude Code, Codex