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 cyperx84/claude-code-plugin-examples --skill commit-message-generatorgit clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examplesWrote 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/cyperx84/claude-code-plugin-examples/commit-message-generator)<a href="https://agentmods.dev/skills/cyperx84/claude-code-plugin-examples/commit-message-generator"><img src="https://agentmods.dev/badge/skills/cyperx84/claude-code-plugin-examples/commit-message-generator/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/cyperx84/claude-code-plugin-examples/commit-message-generator"><img src="https://agentmods.dev/badge/skills/cyperx84/claude-code-plugin-examples/commit-message-generator.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.00020 | $0.01947 |
| Opus 5.5 | $0.00008 | $0.00779 |
| Sonnet 5.5 | $0.00004 | $0.00389 |
| Haiku 4.5 | $0.00002 | $0.00195 |
Grade A, and why
Commit Message Generator 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Generator
Purpose
Generate high-quality commit messages that:
- Follow conventional commit format
- Clearly describe changes
- Provide useful context
- Aid in changelog generation
- Support semantic versioning
When to Use
Invoke this skill when:
- User needs help writing commit messages
- Reviewing staged changes for commit
- Creating standardized team commit messages
- Generating changelog entries
- Teaching commit message best practices
Instructions
Step 1: Analyze the Changes
Examine the git diff to understand:
- Scope of change: What files/modules affected
- Type of change: Feature, fix, refactor, docs, etc.
- Impact: Breaking change or not
- Why: The reason for the change
Step 2: Determine Commit Type
Choose the appropriate conventional commit type:
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Formatting, missing semicolons, etc.
- refactor: Code change that neither fixes a bug nor adds a feature
- perf: Performance improvement
- test: Adding or updating tests
- build: Changes to build system or dependencies
- ci: CI configuration changes
- chore: Other changes that don't modify src or test files
- revert: Reverting a previous commit
Step 3: Identify Scope (Optional)
Determine the scope (area of codebase):
- Component name:
auth,api,ui - Module name:
parser,validator - Feature name:
login,checkout
Step 4: Write the Subject Line
Create a subject line that:
- Starts with type and optional scope:
type(scope): - Uses imperative mood: "add" not "added" or "adds"
- Is no longer than 50-72 characters
- Does not end with a period
- Clearly describes WHAT changed
Step 5: Add Body (if needed)
Include a body for complex changes:
- Explain WHY the change was made
- Describe the previous behavior
- Explain the new behavior
- Justify your approach
- Wrap at 72 characters
Step 6: Add Footer (if needed)
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 · 322 lines · 20 tokens per session scan A 7ae4491c53b5
Commit Message Generator is a skill published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 1y ago), licensed MIT. It adds 20 tokens to every session and 1,947 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.
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.
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…