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/dgalarza/claude-code-workflows/conventional-commitsnpx skills add dgalarza/claude-code-workflows --skill conventional-commitsgit clone --depth 1 https://github.com/dgalarza/claude-code-workflowsWrote 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/dgalarza/claude-code-workflows/conventional-commits)<a href="https://agentmods.dev/skills/dgalarza/claude-code-workflows/conventional-commits"><img src="https://agentmods.dev/badge/skills/dgalarza/claude-code-workflows/conventional-commits.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 | $0.00062 | $0.01847 |
| Opus 5 | $0.00031 | $0.00924 |
| Sonnet 5 | $0.00012 | $0.00369 |
| Haiku 4.5 | $0.00006 | $0.00185 |
Grade A, and why
conventional-commits 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 4d 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commits
This skill provides guidance for writing Git commits that follow the Conventional Commits specification (v1.0.0).
Purpose
Conventional Commits is a specification for adding human and machine-readable meaning to commit messages. It provides an easy set of rules for creating an explicit commit history, which makes it easier to understand project changes and improve collaboration.
When to Use This Skill
Use this skill when:
- Creating Git commits
- Reviewing commit messages in PRs
- Writing clear, structured commit messages
- Collaborating on projects with multiple contributors
Commit Message Structure
Basic Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Examples
feat: add user authentication
feat(api): add JWT token generation
fix: resolve memory leak in image processor
docs: update README with setup instructions
refactor(database): optimize user query performance
Commit Types
Primary Types
feat - A new feature for the user
feat: add export to PDF functionality
feat(api): add webhook signature verification
fix - A bug fix for the user
fix: resolve login redirect loop
fix(api): handle null response from GitHub webhook
docs - Documentation only changes
docs: update API endpoint documentation
docs(readme): add troubleshooting section
style - Changes that don't affect code meaning (formatting, whitespace)
style: format code with StandardRB
style(css): update button padding
refactor - Code change that neither fixes a bug nor adds a feature
refactor: extract user validation to service object
refactor(models): simplify tenant scoping logic
perf - Performance improvements
perf: add database index for user lookups
perf(queries): reduce N+1 queries in artifacts index
test - Adding or updating tests
test: add specs for user authentication
test(integration): add webhook processing tests
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.
- 4d ago First seen · 354 lines · 62 tokens per session scan A b4bf3f201a92
conventional-commits is a skill published in the GitHub repository dgalarza/claude-code-workflows (59 stars, last pushed 7d ago), licensed MIT. It adds 62 tokens to every session and 1,847 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-30.
Other skills, from other repositories
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…
commit
Git commit workflow with precommit hook handling, lint/type checking, README updates, and API reference updates. Use when the user wants to commit changes. Handles precommit hooks that modify files (formatting, linting) by re-staging and retrying. Runs ruff lint and pyright type checks on staged Python files, and…
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…
commit
Create a signed git commit following Conventional Commits, after running /pre-commit and /changelog when appropriate.
commit
Read this skill before making git commits.
et-git
ET git workflow for preparing commits and reviewing changes. Use when checking git status or diff, filtering unrelated files, staging task-scoped changes, writing Chinese commit messages, or synchronizing with remotes using rebase instead of merge.