Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add noahlz/claude-plugins/plugin install dev-workflowWrote 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/noahlz/claude-plugins/preview-commit-message)<a href="https://agentmods.dev/skills/noahlz/claude-plugins/preview-commit-message"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/preview-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/noahlz/claude-plugins/preview-commit-message"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/preview-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.00031 | $0.00644 |
| Opus 5.5 | $0.00012 | $0.00258 |
| Sonnet 5.5 | $0.00006 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
preview-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 8d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this skill to draft a commit message from staged changes without actually committing.
MANDATORY only activate this skill when the user invokes it directly (/preview-commit-message) OR prompts you to draft a message. Examples:
- "write a commit message"
- "draft a commit message"
- "preview a commit message"
- "prepare a commit message"
Follow the workflow steps EXACTLY.
Skill Workflow Checklist
Use this copyable checklist to ensure you follow ALL steps of this skill workflow:
- [ ] 0. Pre-flight check
- [ ] 1. Stage and analyze changes
- [ ] 2. Generate commit message
- [ ] 3. Display proposed message
Skill Context
Workflow Rules & Guardrails
MANDATORY: FOLLOW THESE RULES FOR THE ENTIRE WORKFLOW.
A. Delegation Protocol
When you see DELEGATE_TO: [file]:
STOP -> Use Read tool on the reference file path Execute its instructions exactly (bash commands, parsing, etc.) Return to SKILL.md only after completing reference file instructions
IMPORTANT: Reference files contain Bash tool commands - use them exactly as written - never improvise commands.
B. Narration Control
SILENCE PROTOCOL Only narrate steps with a STEP_DESCRIPTION field. Execute all other steps and tool calls silently - no explanatory text.
Skill Workflow Instructions
0. Pre-Flight Check
HALT if TRUE: Already ran git status/diff/log in parallel OR drafted commit message OR executing system git workflow. STOP skill immediately.
CONTINUE if TRUE: No git commands executed yet. Continue.
1. Stage and Analyze Changes
DELEGATE_TO: ${CLAUDE_PLUGIN_ROOT}/references/stage_and_analyze.md
READ FILE AND FOLLOW INSTRUCTIONS, THEN RETURN HERE
2. Generate Commit Message
DELEGATE_TO: ${CLAUDE_PLUGIN_ROOT}/references/message_guidelines.md
READ FILE AND FOLLOW INSTRUCTIONS, THEN RETURN HERE
Extract COMMIT_SUBJECT and COMMIT_BODY per the reference file instructions. Do NOT display the commit message here. It will be displayed in Step 3. Proceed to Step 3.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago Changed · -2 lines 84f7458fc347
- 1mo ago First seen · 99 lines · 31 tokens per session scan A a53909d0bd47
preview-commit-message is a skill published in the GitHub repository noahlz/claude-plugins (5 stars, last pushed 8d ago), licensed MIT. It adds 31 tokens to every session and 644 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.
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…
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.