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 ErikaAX08/erikas-skills --skill git-commitsgit clone --depth 1 https://github.com/ErikaAX08/erikas-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/erikaax08/erikas-skills/git-commits)<a href="https://agentmods.dev/skills/erikaax08/erikas-skills/git-commits"><img src="https://agentmods.dev/badge/skills/erikaax08/erikas-skills/git-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/erikaax08/erikas-skills/git-commits"><img src="https://agentmods.dev/badge/skills/erikaax08/erikas-skills/git-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.00102 | $0.05608 |
| Opus 5 | $0.00051 | $0.02804 |
| Sonnet 5 | $0.00020 | $0.01122 |
| Haiku 4.5 | $0.00010 | $0.00561 |
Grade A, and why
git-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 10d 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 — 597 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GIT-COMMITS.md — Conventional Commits Engineering Skill
Purpose: this is the operational rulebook an AI agent (or a human) follows to write commit messages, PR/MR titles, and merge messages that make project history easy to read, bisect, and automate against — without the vagueness, mixed concerns, and inconsistency that make git history useless six months later. The full PR/MR body description is the
create-pull-requestskill's job — this file only owns the title format it shares with that skill.This file is self-contained by design. It doesn't assume access to any specific repo's own
CONTRIBUTING.mdor commit conventions. If the target repo has its own documented commit conventions, those win over this file wherever they conflict — this file is the default, not an override.
0. How to use this file
- Before writing a commit message, identify: is this one logical change or several unrelated ones? Use §6 ("Multiple Related vs. Unrelated Changes") to decide whether to split into multiple commits before drafting any message.
- While drafting, follow §2–§4 for type, scope, description, body, and footer. Check §1's non-negotiables first — they catch the mistakes that are easiest to make on autopilot.
- For anything other than a plain new commit (a revert, a merge, an amend, a squash, a hotfix, a dependency bump), check §5 — these have their own shape and their own rules about what's safe to rewrite.
- Before opening a PR, use §7 for the PR/MR title format and §8 for real scenario examples. For
the PR/MR body, use the
create-pull-requestskill instead. - Before delivering the final message, run it through §10 (quality checklist) and follow §11's delivery rules for where the result goes (file vs. terminal).
- If the user's repo has its own commit convention that conflicts with this file, the repo's own convention wins — treat this file as the default for repos with no stated convention of their own, not as an override.
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.
- 10d ago First seen · 597 lines · 102 tokens per session scan A f6f90bd4ad07
git-commits is a skill published in the GitHub repository ErikaAX08/erikas-skills (5 stars, last pushed 11d ago), licensed MIT. It adds 102 tokens to every session and 5,608 once invoked, about $0.0005 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
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
git-commit
Git commit message generator that creates conventional commit messages based on code changes.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
conventional-commit
Guides committing staged (indexed) git files using the Conventional Commits specification and commit message best practices. Use when user mentions commit, git commit, conventional commit, commit message, staged files, indexed files, fixup, or fixup commit. Helps craft well-structured, meaningful commit messages…
wednesday-git
Unified Git workflow. Manages the entire task lifecycle: branch creation (sprint), atomic commits (git-os), and PR opening (pr-create).
conventional-commit
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.