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 asgarovf/locusai --skill conventional-commitsgit clone --depth 1 https://github.com/asgarovf/locusaiWrote 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/asgarovf/locusai/conventional-commits)<a href="https://agentmods.dev/skills/asgarovf/locusai/conventional-commits"><img src="https://agentmods.dev/badge/skills/asgarovf/locusai/conventional-commits/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/asgarovf/locusai/conventional-commits"><img src="https://agentmods.dev/badge/skills/asgarovf/locusai/conventional-commits.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.00038 | $0.00704 |
| Opus 5.5 | $0.00015 | $0.00282 |
| Sonnet 5.5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00070 |
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 1mo 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.
Conventional Commits
When to use this skill
- Writing commit messages for any code change
- Preparing releases with automated changelogs
- Maintaining consistent commit history
- Working in projects that follow semantic versioning
Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types
| Type | Description | Bumps |
|---|---|---|
feat |
New feature for the user | MINOR |
fix |
Bug fix for the user | PATCH |
docs |
Documentation only changes | - |
style |
Formatting, semicolons, etc (no code change) | - |
refactor |
Code change that neither fixes a bug nor adds a feature | - |
perf |
Performance improvement | PATCH |
test |
Adding or fixing tests | - |
build |
Build system or external dependencies | - |
ci |
CI configuration and scripts | - |
chore |
Other changes that don't modify src or test | - |
revert |
Reverts a previous commit | - |
Rules
- Subject line: Imperative mood, lowercase, no period, max 72 chars
- Scope: Optional, in parentheses — identifies the area of change
- Body: Explain what and why, not how. Wrap at 72 chars
- Breaking changes: Add
!after type/scope, orBREAKING CHANGE:footer - Issue references: Use
Closes #123orFixes #456in footer
Examples
feat(auth): add OAuth2 login with Google provider
Implements Google OAuth2 flow using passport-google-oauth20.
Users can now sign in with their Google accounts alongside
email/password authentication.
Closes #142
fix(api): prevent race condition in concurrent order creation
Orders created within the same millisecond could receive
duplicate sequence numbers. Added a database-level unique
constraint and retry logic.
Fixes #891
refactor(db)!: migrate from MongoDB to PostgreSQL
BREAKING CHANGE: All database connection strings must be updated
to use PostgreSQL format. Run `npm run migrate` before starting.
chore: update dependencies to latest versions
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.
- 1mo ago First seen · 99 lines · 38 tokens per session scan A 91402cce1afa
conventional-commits is a skill published in the GitHub repository asgarovf/locusai (23 stars, last pushed 7mo ago), licensed MIT. It adds 38 tokens to every session and 704 once invoked, about $0.0002 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-30.
Other skills, from other repositories
conventional-commits
Write precise Conventional Commits messages from the actual staged diff. Use whenever committing code or asked to write/fix a commit message.
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
changelog-generator
Generate beautiful CHANGELOG.md from git commits following Keep a Changelog format.
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.
Release Engineering
Semantic versioning, changelog generation, and release/hotfix management so releases are predictable and reversible.
changelog
Generate or update a CHANGELOG.md in Keep a Changelog format from real git history. Use when cutting a release, tagging a version, or asked "what changed since…".