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/cuongtl1992/vibe-skills/conventional-commitnpx skills add cuongtl1992/vibe-skills --skill conventional-commitgit clone --depth 1 https://github.com/cuongtl1992/vibe-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/cuongtl1992/vibe-skills/conventional-commit)<a href="https://agentmods.dev/skills/cuongtl1992/vibe-skills/conventional-commit"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/conventional-commit.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.00071 | $0.00710 |
| Opus 5 | $0.00036 | $0.00355 |
| Sonnet 5 | $0.00014 | $0.00142 |
| Haiku 4.5 | $0.00007 | $0.00071 |
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commits
Structured commit messages following the Conventional Commits 1.0.0 specification.
Format
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Types
| Type | When | Example |
|---|---|---|
feat |
New feature | feat(auth): add OAuth2 login |
fix |
Bug fix | fix(cart): correct total calculation |
refactor |
Code restructuring (no behavior change) | refactor(api): extract error handler |
docs |
Documentation only | docs(readme): update setup instructions |
test |
Adding or updating tests | test(order): add unit tests for checkout |
chore |
Build, config, tooling | chore(deps): update Angular to v18 |
style |
Formatting, semicolons (no logic) | style(lint): apply prettier formatting |
perf |
Performance improvement | perf(query): add database index |
build |
Build system changes | build(ci): update Node.js to v20 |
ci |
CI/CD configuration | ci(github): add deploy workflow |
revert |
Revert a previous commit | revert: undo feat(auth) OAuth changes |
Rules
- Description: lowercase, imperative mood, no period at end, max 72 characters
- Scope: optional but recommended, lowercase (module, component, or area)
- Breaking changes: Add
!after type/scope:feat(api)!: remove deprecated endpoint - Body: Separated by blank line, explains "what" and "why" (not "how")
- Footer:
BREAKING CHANGE: <description>orRefs: #123
Workflow
- Check status —
git statusto see what changed - Stage changes — Prefer
git add <file1> <file2>overgit add -A - Analyze changes — Determine type, scope, and description
- Compose message — Follow the format above
- Commit — Use HEREDOC for multi-line messages:
git commit -m "$(cat <<'EOF' feat(auth): add OAuth2 login flow Implements OAuth2 authorization code flow with PKCE. Adds login, callback, and token refresh endpoints. Refs: #142 EOF )" - Verify —
git log --oneline -1to confirm
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 First seen · 65 lines · 71 tokens per session scan A 3c437a216150
conventional-commit is a skill published in the GitHub repository cuongtl1992/vibe-skills (10 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 710 once invoked, about $0.0004 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. 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.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit
Commit current changes with a clear, descriptive message.
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…