Borrowing it
Nothing to install: this file belongs to TashanGKD/Tashan-TopicLab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TashanGKD/Tashan-TopicLab/main/.codex/skills/git-commit-conventions/SKILL.mdgit clone --depth 1 https://github.com/TashanGKD/Tashan-TopicLabWrote 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/tashangkd/tashan-topiclab/git-commit-conventions)<a href="https://agentmods.dev/skills/tashangkd/tashan-topiclab/git-commit-conventions"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-topiclab/git-commit-conventions/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/tashangkd/tashan-topiclab/git-commit-conventions"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-topiclab/git-commit-conventions.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.00059 | $0.01559 |
| Opus 5.5 | $0.00024 | $0.00624 |
| Sonnet 5.5 | $0.00012 | $0.00312 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
git-commit-conventions 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Conventions
Use this skill to keep Git history reviewable and consistent across contributors.
First Checks
Always inspect the current repository rules before changing history or creating a commit:
git status --short --branch
find .. -name AGENTS.md -print
git log --oneline --decorate -n 12
If AGENTS.md or project docs define commit rules, follow the most specific rule for the current working directory. If there are conflicting rules, prefer the project-local rule over a global/default habit.
Before staging or rewriting, inspect scope:
git diff --stat
git diff --name-only
Stage only files that belong to the current task. Do not sweep unrelated worktree changes into a commit.
Branch Names
Use a branch prefix that reflects the requested owner or workflow:
- If the user specifies an owner, use
<owner>/<short-pr-description>, for examplelyy/pr22-arcade-data-relay-openclaw. - If no owner is specified and the environment defines a default branch prefix, use that default.
- Keep branch slugs lowercase, ASCII, hyphen-separated, and descriptive.
- For a PR pulled locally for review or repair, include the PR number when useful:
<owner>/pr22-short-topic.
When pulling an existing PR into a local owner-named branch, keep the PR head branch separate unless the user asks to update the PR head too.
Commit Message Format
Use this base format unless the repository says otherwise:
<type>(<scope>): <English message>
Allowed common types:
feat, fix, chore, refactor, docs, test, build, ci, perf, style, revert
Choose the type from the actual change:
feat: adds a new user-visible or API-visible capability.fix: corrects broken behavior, compatibility, routing, recovery, or data handling.docs: changes documentation only.test: adds or updates tests only.chore: maintenance with no behavior change.refactor: restructures code without intended behavior change.buildorci: build system or automation changes.perf: performance improvement.style: formatting or presentation-only code changes.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 194 lines · 59 tokens per session scan A 909c63249843
git-commit-conventions is a skill published in the GitHub repository TashanGKD/Tashan-TopicLab (6 stars, last pushed 10d ago), licensed MIT. It adds 59 tokens to every session and 1,559 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-31.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.