Borrowing it
Nothing to install: this file belongs to quality-screener/quality-screener-mcp-server. 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/quality-screener/quality-screener-mcp-server/main/.claude/skills/commit-message/SKILL.mdgit clone --depth 1 https://github.com/quality-screener/quality-screener-mcp-serverWrote 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/quality-screener/quality-screener-mcp-server/commit-message)<a href="https://agentmods.dev/skills/quality-screener/quality-screener-mcp-server/commit-message"><img src="https://agentmods.dev/badge/skills/quality-screener/quality-screener-mcp-server/commit-message.svg" alt="Measured on agentmods" 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.00070 | $0.02305 |
| Opus 5 | $0.00035 | $0.01153 |
| Sonnet 5 | $0.00014 | $0.00461 |
| Haiku 4.5 | $0.00007 | $0.00231 |
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 7d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Crafter
Produce a single commit message that follows Conventional Commits 1.0.0 and always names the affected component in scope. This is the only style this project accepts.
The Format
<type>(<component-scope>): <short imperative summary>
[optional body — why, not what]
[optional footer(s) — breaking changes, refs]
Required:
<type>— one of the canonical types below.(<component-scope>)— never omit the component scope. This is the project's hard rule on top of Conventional Commits. Pick the smallest meaningful scope (see "Choosing the Component Scope").: <short imperative summary>— ≤ 72 chars, lowercase, imperative mood ("add" not "added"/"adds"), no trailing period.
Optional:
- Body separated from the subject by one blank line. Wrap at ~100 chars. Focus on why, hidden constraints, trade-offs — not a re-statement of the diff.
- Footers separated from the body by one blank line.
BREAKING CHANGE: <description>footer or!after the type/scope (feat(api)!: ...) when the change is incompatible.
Allowed Types
Use exactly one. Order of preference when ambiguous: pick the type that captures the user-visible effect, not the file you touched.
| Type | Use when |
|---|---|
feat |
A new capability visible to the user, an API, or a developer |
fix |
A bug fix (regression or pre-existing) |
refactor |
Internal restructuring without behavior change |
perf |
Performance-only change |
test |
Adding or fixing tests only |
docs |
Documentation only (READMEs, CLAUDE.md, comments) |
style |
Whitespace / formatting only (rarely needed; ruff/prettier output) |
build |
Build system, dependency, packaging (uv, npm, Docker, Alembic env) |
ci |
CI configuration only |
chore |
Misc maintenance that doesn't fit elsewhere; avoid as a catch-all |
revert |
Reverts a previous commit; body must reference the SHA being reverted |
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.
- 7d ago First seen · 250 lines · 70 tokens per session scan A 84bd584b430a
commit-message is a skill published in the GitHub repository quality-screener/quality-screener-mcp-server (0 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 2,305 once invoked, about $0.0003 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-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-next. 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.
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.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…