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 rlespinasse/agent-skills --skill conventional-commitgit clone --depth 1 https://github.com/rlespinasse/agent-skillsWrote 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/rlespinasse/agent-skills/conventional-commit)<a href="https://agentmods.dev/skills/rlespinasse/agent-skills/conventional-commit"><img src="https://agentmods.dev/badge/skills/rlespinasse/agent-skills/conventional-commit/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/rlespinasse/agent-skills/conventional-commit"><img src="https://agentmods.dev/badge/skills/rlespinasse/agent-skills/conventional-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 177 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 179 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 285 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00091 | $0.02747 |
| Opus 5.5 | $0.00036 | $0.01099 |
| Sonnet 5.5 | $0.00018 | $0.00549 |
| Haiku 4.5 | $0.00009 | $0.00275 |
Grade A, and why
conventional-commit 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 5d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Staged Files with Conventional Commits
You are helping the user commit their currently staged (indexed) git files using the Conventional Commits specification and commit message best practices.
Pre-flight Checks
Before crafting a commit message, always:
- Run
git statusto see what files are staged - Run
git diff --cachedto review the actual staged changes - If nothing is staged, inform the user and stop — do not create an empty commit
Conventional Commit Format
<type>[optional scope]: <subject>
[optional body]
[optional footer(s)]
Types
| Type | When to use |
|---|---|
feat |
A new feature or capability |
fix |
A bug fix |
docs |
Documentation-only changes |
style |
Formatting, whitespace, semicolons — no logic change |
refactor |
Code restructuring without behavior change |
perf |
Performance improvement |
test |
Adding or updating tests |
build |
Build system or external dependency changes |
ci |
CI/CD configuration changes |
chore |
Maintenance tasks (deps update, tooling, config) |
revert |
Reverting a previous commit |
Note: Comment-only changes (adding, updating, or removing code comments) should use style or
chore — never feat or fix. Keep commit messages concise; do not describe individual comments.
Scope
- Optional, but recommended when the change targets a specific module, component, or area
- Use lowercase, kebab-case:
feat(auth):,fix(api-client): - Keep consistent with the project's existing scope conventions
- Check recent git log (
git log --oneline -50or more) for scope patterns already used in the project - Also note whether the project actually uses conventional commits — if not, adapt to the project's style
Subject Line Rules
- Imperative mood: "add feature" not "added feature" or "adds feature"
- Lowercase first letter: "add feature" not "Add feature"
- No period at the end
- 50 characters or less — hard limit at 72
- Complete the sentence: "If applied, this commit will <subject>"
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.
- 5d ago Changed · +1 lines · +17 tokens per session 043e8b786c50
- 1mo ago First seen · 306 lines · 74 tokens per session scan A 0c9b647509e5
conventional-commit is a skill published in the GitHub repository rlespinasse/agent-skills (13 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 2,747 once invoked, about $0.0004 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
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
git-commit
Git commit message generator that creates conventional commit messages based on code changes.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
git-commits
Write clear, semantic git commit messages and PR/MR titles following Conventional Commits. Use when the user asks to write commit messages, format git history, improve commit quality, or set a PR/MR title, or mentions "commit message", "conventional commits", "merge message", or "git history". For the full PR/MR body…
wednesday-git
Unified Git workflow. Manages the entire task lifecycle: branch creation (sprint), atomic commits (git-os), and PR opening (pr-create).
conventional-commit
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.