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 agentmods add skills/noahlz/claude-plugins/preview-commit-messagenpx skills add noahlz/claude-plugins --skill preview-commit-messagegit clone --depth 1 https://github.com/noahlz/claude-pluginsWhat 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 | $0.00031 | $0.00650 |
| Opus 5 | $0.00015 | $0.00325 |
| Sonnet 5 | $0.00006 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
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 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 — 99 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
SKILL_BASE_DIR: ${CLAUDE_SKILL_DIR}
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: ../../references/stage_and_analyze.md
READ FILE AND FOLLOW INSTRUCTIONS, THEN RETURN HERE
2. Generate Commit Message
DELEGATE_TO: ../../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.
- 2d 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 3d ago), licensed MIT. It adds 31 tokens to every session and 650 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…