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.
npx skills add MasonEgger/bpe-claude-code-plugin --skill commit-messagegit clone --depth 1 https://github.com/MasonEgger/bpe-claude-code-pluginWrote 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/masonegger/bpe-claude-code-plugin/commit-message)<a href="https://agentmods.dev/skills/masonegger/bpe-claude-code-plugin/commit-message"><img src="https://agentmods.dev/badge/skills/masonegger/bpe-claude-code-plugin/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/masonegger/bpe-claude-code-plugin/commit-message"><img src="https://agentmods.dev/badge/skills/masonegger/bpe-claude-code-plugin/commit-message.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.00018 | $0.00738 |
| Opus 5.5 | $0.00007 | $0.00295 |
| Sonnet 5.5 | $0.00004 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Command
Inspect the staged changes, write a commit message that captures the why of the change, and save it to commit-msg.md at the repo root for the user to feed into git commit -F commit-msg.md.
Step 1: Inspect the Changes
Run these in parallel:
git status: see all untracked files and modifications.git diff --staged: the exact set of changes that will be committed.git diff: what is modified but NOT yet staged. Do not narrate work that is in this diff but not the staged one.git log --oneline -10andgit log -3 --pretty=full: match the repository's commit-message style and signing/conventions.
Step 2: Identify the Why
Analyze the staged diff. Answer:
- What problem does this commit solve, or what capability does it add?
- Why is this approach the right one, only if non-obvious from the code.
- Was anything explicitly NOT changed that a reader might expect (deferred, out of scope, separate commit)?
If the user passed an argument, treat it as a focusing hint; bias the message toward the threads they named, not the full diff.
Step 3: Compose the Message
Format:
- Subject line: imperative mood, ~50 characters target, ~72 characters hard cap. No trailing period.
- Blank line.
- Body: one or more paragraphs, wrapped at ~72 characters. Lead with the why (the problem solved or the capability added), then the what only when not obvious from the diff. Use bulleted lists where they actually help; flowing prose otherwise.
Avoid:
- Restating WHAT the diff already says when the WHY is obvious.
- Listing every file changed.
- Marketing language ("dramatically improves", "robust", "comprehensive", "powerful").
- Self-references like "this commit" or "this PR"; the message is the commit.
- Co-authored-by or AI-attribution trailers unless the user explicitly asks.
- Bumping versions, regenerating lockfiles, or any side action; this command only writes the message.
Match the repository's existing style observed in git log (subject-line case, conventional-commits prefix or not, trailers).
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 · 80 lines · 18 tokens per session scan A 09ddc93d841f
commit-message is a skill published in the GitHub repository MasonEgger/bpe-claude-code-plugin (7 stars, last pushed 27d ago), licensed MIT. It adds 18 tokens to every session and 738 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-31.
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.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
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…