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/aigengame/cli-agentic-workflow/git-conventional-commitsnpx skills add aigengame/cli-agentic-workflow --skill git-conventional-commitsgit clone --depth 1 https://github.com/aigengame/cli-agentic-workflowWrote 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/aigengame/cli-agentic-workflow/git-conventional-commits)<a href="https://agentmods.dev/skills/aigengame/cli-agentic-workflow/git-conventional-commits"><img src="https://agentmods.dev/badge/skills/aigengame/cli-agentic-workflow/git-conventional-commits.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.00035 | $0.00889 |
| Opus 5 | $0.00017 | $0.00445 |
| Sonnet 5 | $0.00007 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
git-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 4d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill enables the code agent to formulate precise, standard-compliant Git commit messages and branch names based on the Conventional Commits 1.0.0 specification. Adhering to this standard allows automated tools to parse commit histories, bump semantic versions (Major/Minor/Patch) accurately, and generate clean changelogs.
Requirements & Triggers
- Trigger: Whenever the agent completes a task, implements a feature, fixes an issue, or refactors code and is ready to execute
git commit. - Pre-requisite: Understand the scope of changes and know the associated GitHub Issue number (if any).
Guidelines & Rules
1. Commit Message Structure
Every commit message must strictly follow this structural pattern:
<type>(<scope>): <subject>
<body>
<footer>
- (Required): Must be one of the structural keywords defining the change intent.
- (Optional): A noun describing the affected section of the codebase enclosed in parentheses (e.g., auth, api, parser).
- (Required): A succinct description of the change. Use imperative mood ("add" not "added"). No period . at the end.
2. Allowed Commit Types ( )
| Type | Definition | SemVer Impact |
|---|---|---|
feat |
A new feature implemented in the codebase | Minor |
fix |
A bug fix implemented in the codebase | Patch |
docs |
Documentation only changes (e.g., markdown files) | None |
style |
Changes that do not affect the meaning of the code (white-space, formatting, etc.) | None |
refactor |
A code change that neither fixes a bug nor adds a feature | None |
perf |
A code change that improves performance | None |
test |
Adding missing tests or correcting existing tests | None |
build |
Changes that affect the build system or external dependencies | None |
ci |
Changes to CI configuration files and scripts | None |
chore |
Other changes that don't modify src or test files (e.g., .gitignore) | None |
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.
- 4d ago First seen · 85 lines · 35 tokens per session scan A 88125a16c801
git-conventional-commits is a skill published in the GitHub repository aigengame/cli-agentic-workflow (20 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 889 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
secrets-scan
Pre-commit secrets detection with pattern-based scanning for API keys, tokens, passwords, private keys, and connection strings. Self-contained — no external tools required.
git-commit-guide
通用 Git 提交原则——提交时机、信息格式、提交前自检。Use when the user is about to commit code, asks about commit messages, or after completing a functional unit of work.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
proposal-filing
File a new Lorekeeper proposal ticket — create markdown, create GitHub issue, commit, push. Use when requesting a new feature, filing a bug, or submitting a product idea.
fix-pr-commit-titles
Bulk-rewrite commit titles on a PR branch to match [LKPR-N] format using filter-branch — avoids per-commit hook re-runs.
after-changes
Post-change checklist to run after any set of code edits. Runs three steps in sequence: (1) code review via /simplify, (2) README consistency check and update, (3) git commit. Trigger on phrases like "review and commit", "after-changes", "wrap up changes", "commit my changes", or when the user says to remember to do…