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 LichAmnesia/awesome-antigravity-skills --skill conventional-commitsgit clone --depth 1 https://github.com/LichAmnesia/awesome-antigravity-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/lichamnesia/awesome-antigravity-skills/conventional-commits)<a href="https://agentmods.dev/skills/lichamnesia/awesome-antigravity-skills/conventional-commits"><img src="https://agentmods.dev/badge/skills/lichamnesia/awesome-antigravity-skills/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/lichamnesia/awesome-antigravity-skills/conventional-commits"><img src="https://agentmods.dev/badge/skills/lichamnesia/awesome-antigravity-skills/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.00047 | $0.00510 |
| Opus 5 | $0.00023 | $0.00255 |
| Sonnet 5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
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 11d 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.
What it actually says
Conventional Commits
When creating a commit message, follow Conventional Commits 1.0.0.
When to use this skill
- The user asks to commit staged or unstaged changes.
- The user asks "write a commit message for this diff".
- The repo has
commitlint,husky, or aCONTRIBUTING.mdmentioning Conventional Commits.
How to use it
- Inspect the change first:
git diff --staged(orgit diffif nothing is staged). Never invent a message without reading the diff. - Pick the type from the actual change, not the file names:
feat— user-visible behavior addedfix— user-visible bug fixedrefactor— behavior-preserving restructuredocs,test,build,ci,chore,style,perf
- Add a scope when the repo already uses them (check
git log --oneline -20for the house style). - Subject line: imperative mood, lowercase after the colon, no trailing period, ≤ 72 chars.
- Body (optional): explain why, wrap at 72. Footer:
BREAKING CHANGE:or issue refs (Closes #123).
Decision tree
- Mixed unrelated changes in one diff → propose splitting into multiple commits instead of one vague
chore. - Change is a revert → use
revert:and reference the reverted SHA. - Unsure between
fixandrefactor→ does an end user observe the difference? Yes =fix, no =refactor.
Done means
git log -1 --format=%s matches ^(feat|fix|refactor|docs|test|build|ci|chore|style|perf|revert)(\(.+\))?!?: .+ and the message honestly describes the diff.
Part of awesome-antigravity-skills. Browse more Agent Skills at orangebot.ai/skills.
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.
- 11d ago First seen · 41 lines · 47 tokens per session scan A 18ae0fc072f5
conventional-commits is a skill published in the GitHub repository LichAmnesia/awesome-antigravity-skills (7 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 47 tokens to every session and 510 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-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
conductor-revert
Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.
conventional-commits
Enforce, validate, lint, and manage Conventional Commits across git repositories. Generates semantic changelogs and installs git hooks. Use this skill whenever the user mentions commit messages, commit conventions, conventional commits, semantic versioning, changelogs, commit linting, git hooks for commits, or wants…
git-pushing
Stage all changes, create a conventional commit, and push to the remote branch. Use when explicitly asks to push changes ("push this", "commit and push"), mentions saving work to remote ("save to github", "push to remote"), or completes a feature and wants to share it.
commit
Detect the repo's commit convention (Conventional Commits, Gitmoji, or a custom template) and create commits. Use when asked to commit, write a commit message, stage and commit changes, or commit and push work.
git-commit-formatter
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.