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 | $0.00019 | $0.00352 |
| Sonnet 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 9d 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.
- 9d 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 6mo ago), licensed MIT. It adds 38 tokens to every session and 704 once invoked, about $0.0002 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
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-automation
Expert Git workflow automation for commit message generation, branch naming, PR description writing, changelog generation, merge conflict resolution, and release management. Activates when users say "write a commit message", "create a PR", "generate changelog", "branch name for", "resolve merge conflict", "cut a…
changelog-generator
Generate beautiful CHANGELOG.md from git commits following Keep a Changelog format.
atmos-git
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims, signed commits, managed workdirs, fork-PR trust gate, and auth via identities or github/sts.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
release-management
Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.