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 siracalaks/claude-code-antigravity-a-z --skill conventional-commitgit clone --depth 1 https://github.com/siracalaks/claude-code-antigravity-a-zWrote 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/siracalaks/claude-code-antigravity-a-z/conventional-commit)<a href="https://agentmods.dev/skills/siracalaks/claude-code-antigravity-a-z/conventional-commit"><img src="https://agentmods.dev/badge/skills/siracalaks/claude-code-antigravity-a-z/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.1 | $0.00025 | $0.00191 |
| Opus 5 | $0.00013 | $0.00096 |
| Sonnet 5 | $0.00005 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
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 8d 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 Commit
When you create a git commit, follow these rules:
- Start the subject line with one of: feat, fix, chore, docs, refactor, test, perf
- Add a colon and a space, then a short imperative summary, no period
- Maximum 72 characters
- If the change is breaking, add ! before the colon
Examples
Input: Added user authentication with JWT tokens Output: feat(auth): implement JWT-based authentication
Input: Fixed null pointer in date parser Output: fix(parser): handle null input in formatDate
DON'T
- Never use vague messages like "WIP" or "tmp"
- Don't say "this commit" in the body; it's obviously a commit
- Don't capitalize the type
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.
- 8d ago First seen · 28 lines · 25 tokens per session scan A ce52b5871d6b
conventional-commit is a skill published in the GitHub repository siracalaks/claude-code-antigravity-a-z (7 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 191 once invoked, about $0.0001 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
cross-repo-cache
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
caveman-commit
Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…
commit-and-push
Create a well-formatted git commit and push to remote repository.